Writing / Reading Logs To Multiple Targets

How logs are writing / reading multiple targets by the Orchestrator?

Writing / Reading logs to multiple targets: Open the UiPath.Orchestrator.dll.config ("web.config" for versions older than 2020.4) file in the installation location of the Orchestrator and verify or configure the rules.

Writing to Targets: Rules can be defined in below two ways,

  1. Multiple targets:

Note: If any one of the targets is not configured properly, logs will not write to any targets.

Logs are writing to the multiple targets such as Database, Elastic search, Kafka, etc.., But UiPath supports Database and Elastic search targets which is tested.

  • Rules in the UiPath.Orchestrator.dll.config/web.config file

In above rule defined, information logs goes to the Elastic search and error logs go to the database.

Explanation: In first line of the rule, the information logs (Minlevel=”info”) will go to the Elastic Search target (WriteTo=”robotElasticBuffer”) and as defined (final=”false”) it goes to the next line and check the another target and write only error logs (Minlevel=”Error”) to the database and as defined (final=”true”) so it will not check next target it breaks.

Configuration of the Elastic search target.

  1. Single target:

Logs are writing to single target either database or elastic search, in above example rules is defined for the database so all the logs will push to the database.

Reading from Targets

  • Reading from Multiple Targets

Orchestrator reads by default from the first line in the target which is defined in the rules. In the above example it read the logs from the Elastic Search.

Note: It will not read the logs from the second target.

  • Reading from Single Target

It Reads the only from the database target.

For more details on logs: