Search specific log fields values in orchestrator

Help Studio
, , ,
1

Hello Community

I’ve been searching for ways that I can make my logging more effective. One thing I often found myself doing is trying to search for a specific transaction logs messages, and when working with large amount of transactions it can get daunting trying to find all the logs for that transaction if one don’t have a good logging system. So I was wondering if the activity “Add Log Fields” could help me with this. The main question I have is if it is possible to search for log fields values in my orchestrator logs results for a certain process transaction?

Let’s say I have a REF process that basically works with a client base, where each client is a transaction, and every time a start a new transaction i add a log field called “client” with the name of the client as value. Now once the process is finished I want to find all the logs wherein “client” was equal to “Jhon”. How can I achieve this? Because I haven’t seen this search capability in the logs on orchestrator.

Hopefully someone can provide me with some clarity… Thank you!

2

hi @Luis_Fernando ,

You could try “Add Log Fields” and run the process.
In Orchestrator, navigate to Folder>Robot>View Logs>Export and open in Excel.
I’m curious to see if the additional log field will come up as a new column there which you can then filter as you like.

A few other general suggestions:

  1. Insert log message at the beginning and end of each workflow (eg. “31_Process1.xaml begins…”)
  2. Break up large workflows into smaller workflows
  3. Insert log message with input argument contents at beginning of each workflow
  4. If you are using REF, you should already be working with a queue and each transaction item have specific content called “client” which collects this information. At the end of transaction, you can record additional fields under “Output Data” or “Analytics Data”. After the transaction is processed, you can then navigate to Queues>View Transactions>View Details to check the status of the transaction.
  5. For each process, create a diagram of how each workflow is connected to other workflows to help with future troubleshooting.
3

Hello @Keegan_Kosasih, thank you very much for your response

I appreciate those recommendations, I find them really interesting. Based on your answer I see there is no direct way of filtering the logs inside of orchestrator, so I would have to download logs then.

4

Yes, as far as I’m aware the Orchestrator web interface only supports basic viewing and searching of logs.