Orchestrator - Logs at Queue Item level

Feedback Orchestrator
, ,
1

We have processes where we insert specific log messages in order to monitor the execution on items. Right now we can view the logs associated with a specific job run but in order to debug a specific error for an item in the queue we need to:

  1. Search for the item and see which was the start and the end of execution for that particular item
  2. Search for the specific job which contain the logs for the item
  3. Search for the portion in the log where we have the information related to the specified item

This can take up to 20 minutes when you are looking for an older item which was run a week ago for example.

We are using the reframework so we have the information when a specific item is picked up from the list.

It will be nice if you can connect the part of the logs where a particular item was worked with the item itself and create an additional tab in the queue item information where to display this log information. In this way the debugging will be done much easier having all the information at queue item level.

3

@CristianZachiteanu

A small work around of a way to hndle this in the mean time

Add the unique key as a log field …default you have already two fieds in re frameowrk…we can add the unique value to those fields and logs can be filtered using those fields…this way it can be faster as well

Cheers