The Logs page displays logs generated by Robots. To make it easier to sift through all the generated data, you can view it in a filtered manner, as follows:
- all logs generated by an indicated Robot, from the Robots page
- all logs generated by a Robot within an indicated job, from the Jobs page
For more information, see Managing Logs in Orchestrator.
Logs can be sent to ElasticSearch and/or to a local SQL database. By default, they are both used. When using both ElasticSearch and SQL, they do not affect each other if one of them encounters a problem.
These parameters can be changed from the
web.config file (
C:\Program Files (x86)\UiPath\Orchestrator). For more information, see Logging Configuration.
If you maintain more than two million log entries in the SQL database, you might have some performance issues. For more than two million log entries, we recommend using ElasticSearch.
If you set the
web.config file to send Robot logs only to ElasticSearch, the Logs page is empty.
Messages are logged on the following levels: Trace, Debug, Info, Warn, Error and Fatal.
Custom messages can also be sent to this page from Studio, with the Log Message activity. The messages can be logged at all the levels described above and should be used for diagnostic purposes.
For example, in the screenshot below, you can see that we logged a custom message at a Fatal severity level.
All logs can be exported to a .csv file, by clicking the Export button. The filters applied to this page are taken into account when this file is generated. For example, if you set to view logs only from the last 30 days with an Info severity level, only the entries that meet these criteria are downloaded.
Please note that logs may not be in the proper order only in the following scenario:
- There are two or more robot log entries with almost equal timestamps - they are equal up to the millisecond (time expressed as
yyyy-MM-dd HH\:mm\:ss.fffis the same), but differ in the millisecond's subunits (the last four values in
yyyy-MM-dd HH\:mm\:ss.fffffffare different).
- The logs are viewed in Orchestrator with the default sort order in the grid (sort by Time descending).
However, the database and exported .csv file are not affected.