Debugging with the orchestrator is frustrating

[jeevith (Jeevith Hegde, Ph.D.)]

Hi @kbak,

I second that and I feel your pain.

After some very frustrating days we decided it was enough. Orchestrator does not help us when we need a hotfix and are stuck with parsing logs to find the needle in the haystack. The search function is great but when we are a small team we need results quick.

We use a custom dashboard on Splunk and get all the diagnostic metrics of robot executions, failures and time usage for every process and can slice and dice the data to our liking.

I did pen down the entire process in this thread.

Logs - ElasticSearch

Anyone who uses ElasticSearch? What’s the real benefit when comparing to the Orchestrator standard dashboard, Orchestrator standard mail notifications (when job failures take place), Orchestrator job logs and SQL/Text files that house it by default? Besides Elastic, is there any alternative solution that you are either using currently or have heard about? I know how Elastic/Kibana works, but just trying to get some insights/experiences… Thanks a lot in advance!

You can choose any software does not need to be Splunk. Even good old excel will be good enough. I cannot talk about UiPath insights as I have not tried it myself and UiPath selling it as another license to me is not a good model in the long run. Too many licenses!

My suggestion is that you take some time to build up a good Nlog format and then start using any visualize / analysis software to ingest and make sense of your logs.

Failure spotting and reporting becomes a simple chore thereafter.

Hope this helps you.