Robot logs are not visible in Orchestrator if Elasticsearch is configured

[Alex_Voloshyn]

The logs are not visible in Orchestrator and “An error has occurred” message is displayed if Elasticsearch is enabled for Robots.
Orchestrator version: 2018.4.5

The only way I can make it work if I remove a value from uri parameter of robotElastic
<target xsi:type="ElasticSearch" name="robotElastic" uri="http://localhost:9200" requireAuth="false" username="" password="" index="${event-properties:item=indexName}-${date:format=yyyy.MM}" documentType="logEvent" includeAllProperties="true" layout="${message}" excludedProperties="agentSessionId,tenantId,organizationUnitId,indexName"/> in Web.config (replacing it with uri="").

The question is it possible to see the logs both in the Orchestrator and in the ElasticSearch?

I tried another approach suggested here and clean up C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\ folder on the robot’s server but that did not help.

Looks like a similar issue described here but I performed a clean installation without an upgrade.

[loginerror (Maciej Kuźmicz)]

Hi @Alex_Voloshyn

Welcome to our UiPath Forum!

It is possible that you will need to contact our technical support for them to investigate further.

[Alex_Voloshyn]

Resolution:
Change the target name under robotelasticbuffer from robotelastic(default) to robotelastic1.

<target xsi:type="ElasticSearch" name="robotElastic1" uri="http://localhost:9200" requireAuth="false" username="" password="" index="${event-properties:item=indexName}-${date:format=yyyy.MM}" documentType="logEvent" includeAllProperties="true" layout="${message}" excludedProperties="agentSessionId,tenantId,organizationUnitId,indexName"/>

This change should not have any impact on any behavior of robot/orchestrator.