When we fetch log entry from Incident via REST API, we are getting log entry id in alpha-numeric format.
For e.g. when we hit https://api.pagerduty.com/log_entries
in that we are getting log entry id like below
so here we can see that id is alpha-numeric.
We basically need to do numeric operations on revision Id but as this is alpha-numeric we can’t do so is there any way where any other field is exposed from API which is in numeric format and having revision ID.
Additionally we want to know that is order of log entry is guaranteed always ?
Like if Entity E1 is updated twice at same time T1 so basically there are 2 updates on that incident within same. Now int this case, when we get audits via https://api.pagerduty.com/log_entries will this always be on same order which means if I execute any number of time it will return same result always ?