User16445912622657480582 (Customer) asked a question.
How to use x-okta-request-id values for troubleshooting
How does one use the x-okta-request-id values that come back on okta api requests for troubleshooting? Is there a specific field in the System Log this values correlates with?
The documentation I can find on it just says "You can use this value to correlate events from the System Log events.". But the system log page does not have any further details about how one uses the value from x-okta-request-id.
https://developer.okta.com/docs/reference/core-okta-api/*request-debugging
Hi @User16445912622657480582 (Customer) , Thank you for reaching out to the Okta Community!
Just to clarify a bit what Hengfeng mentioned.
You can leverage the requestID in a System Log query (Okta Admin Dashboard → Reports → System Logs) to pin-point the event.
For example, leveraging the following syntax:
transaction.id eq “xxxe9abcb714cb4e2912822bc146"
OR
debugContext.debugData.requestId eq “xxxe9abcb714cb4e2912822bc146"
If you are leveraging the Okta System Logs API, then you would use it as part of a filter parameter. For example:
{{url}}/api/v1/logs?filter=transaction.id eq “xxxe9abcb714cb4e2912822bc146"
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Ask the Experts: Now Thru 1/31 Okta FastPass Engineering and Product Teams Answer Your Questions