Elastic Search and Orchestrator Logs

Hi Team,

Could you please help me to understand about Elastic Search and Orchestrator Logs?

What is Elastic Search?

Where does orchestrator logs get stored?

Need quick help to understand it.

Thanks
Ritesh

@Ritesh_Burman

Take a look below thread it might help,

Happy Automation,
YK

Hi @Ritesh_Burman

Let’s answer your questions:

  1. ElasticSearch is an open-source search and analytics engine. It was designed to store large amounts of log data and makes it easier for you to search and filter through that data a lot easier than manually. You can then also use Kibana for the visualization of that data allowing you to create dashboards etc.
  2. By default all robot logs are sent to the Logs table of the default Orchestrator Database. For on-prem, that is your SQL Database connected. For Automation Cloud, that is UiPath’s own cloud-based Database (you don’t have control over but you can access via the Monitoring tab or by API).
  3. You can integrate with ElasticSearch to store log information in ElasticSearch for on-prem installations, or alternatively for Automation Cloud, you can use UiPath Insights to visually see that information or to create custom dashboards.

Hope this helps.

Hi @Ritesh_Burman

Elastic Search is basically used by UiPath to store and search robot logs quickly, especially when there are a lot of logs being generated. Orchestrator logs are usually stored either in the SQL database or in Elastic Search, depending on how the environment is configured. In enterprise setups, Elastic Search is commonly used because searching and monitoring logs becomes much faster and easier.