How to resolve if there are No Logs in ElasticSearch?
Approach 1#:
Note: This will impact all the robots, i.e. logs for all the robots will not be seen in Elastic Search.
The target defined is not correct; to validate that the target is defined correctly:
- Search the parameter "target" in Uipath.Orchestrator.dll.config.
- Verify if the type is "Elasticsearch" as seen in the below snapshot.
- Verify the URI defined for the target. URI represents the Elasticsearch URL.
- Restart the Website in IIS.
Approach 2#:
Note: If a specific Robot is impacted, and logs are not seen in Elasticsearch
- Log in to the impacted robot servers and clear the log file from the location: C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data and restart Robot service
- Deleting the execution log data will cause a permanent loss of logs for the impacted time frame.
Approach 3#:
Note: This applies if the disk space in the Elasticsearch server on the data drive is over 85%.
When the data node drive on the Elasticsearch server reaches 85%, the node changes all the index to read-only and stops accepting new logs. To fix this, follow the below steps:
- Delete the old index to make space for new logs.
- Set read-only property to false: do this by setting the below property in the elasticsearch.yml file
- read_only_allow_delete: false
Approach 4#
Note: This applies if the tenant is renamed manually from the database.
If a tenant is renamed from the backend by altering the tenant name from "Tenants" table, the change will be effective in most areas of the Orchestrator. However, logging uses a parameter called "LoggingIndex" from dbo.settings table to identify the index pattern. The logs will be sent to Elasticsearch with the old name until the name is updated in the dbo.settings table.