Using API for reading Robot Logs

Hi All,

Is it any way we can reading robot logs via API?

yes, you can use swagger/ [RobotLogs] method, to access RobotLogs through API Calls

Is there any documentation for it?

Hi @hadi2002

Of course, see here: :slight_smile:
https://orchestrator.uipath.com/v2019/reference

1 Like

Thanks @loginerror

1 Like

Hi @loginerror and @sankar.kuna ,

I receive a 500 Error when using the [odata/RobotLogs] API with an organizational unit ID.
Other APIs such as [odata/Jobs] work fine and deliver results. I use an admin user for all requests having the respective permissions.

The RobotLogs API works fine when using the community edition (w/o organizational units).

Is there any known issue with organizational units for this endpoint or is there anything that needs to enabled?

Hi @loginerror, @sankar.kuna ,

a follow-up question to the previous one:
Could it be that filtering at the Robot Log API does only work for “RobotName”, but not for other fields such as “ProcessName”, “Level”, “TimeStamp”, etc.?

Appreciate your help!

Hi @Johannes.M
Have you found any solution for filtering on the basis of TimeStamp,Level and ProcessName
Please suggest

Thanks
Gopal Tewari

Refer …

https://docs.uipath.com/orchestrator/v2019/reference/robots-requests

…and…

Note

GET requests for Robot logs stored using Elasticsearch only retrieve the first 10000 entries. This is due to an Elasticsearch limitation, and it does not occur if you are using SQL.
Using $top and $skip parameters which go beyond the 10000 limit returns the following error message: Depth of pagination is limited in Elasticsearch by the max_result_window index setting. Make sure skip + take is lower than 10000.

Only the following condition-verb combinations are supported when parameterizing requests for Robot logs stored using Elasticsearch: RobotName eq , JobKey eq , MachineId eq , Level ge , TimeStamp gt .