Problem with absolute timestamp in export log

Feedback Orchestrator
,
1

Hello,

when I export the logs from the Orchestrator the absolute timestamp will not be exported.
It has the same format as the normal timestamp…
But I need the milliseconds for my analysis.

The csv appears in this way:
time;time (absolute);
19.01.2024 13:00:35;19.01.2024 13:00:35;

Has anybody encountered this problem?

3
  • UiPath Orchestrator’s API can be used to fetch logs with more detailed information, potentially including more precise timestamps. The Orchestrator API provides endpoints for retrieving logs (/odata/RobotLogs or /odata/Logs depending on your version), which might include more detailed timestamps than those available through the CSV export.
  • To use the API, you would send a GET request to the appropriate endpoint and parse the JSON response. The JSON response is likely to include timestamps in a more precise format.

To fetch logs via the Orchestrator API, you would first authenticate to get a bearer token and then use that token to make a GET request to the logs endpoint. Here’s a conceptual example of how the process might look:

POST /api/account/authenticate
{ "tenancyName": "your_tenancy", "usernameOrEmailAddress": "your_username", "password": "your_password" }

GET /odata/RobotLogs
Authorization: Bearer your_access_token