When looking through the logs in UNIFYBroker, I find it difficult to associate all log messages that relate to one request that has been executed. This is particularly difficult on a busy live system where multiple operations are happening in parallel and log entries are interleaved.
It would be very beneficial to include a request identifier on every log entry, to indicate which request the log entry relates to. That way all the log entries for one request could be extracted and viewed separately, to give a convenient and complete picture of all of the logged outcomes of that request. It would also make it possible to generate a high level request list summary, by extracting just the first log entry for each request. This would be incredibly useful when investigating problems and logging voice tickets.
|Timestamp||Request Description||Request ID|
|2019-07-20 01:39:49||Request to manually queue a baseline synchronization job on link started. Request to manually queue a baseline synchronization job on link Chris21 DET started.||ae4dffd3-f857-4074-957b-5be0a10b201b|
|2019-07-20 01:47:40||Request to sync adapter to locker started. Synchronization job started syncing 42942 changes on the 'Chris21 DET' link from the adapter to locker.||017f4072-470e-47fd-83cb-13b9c9d03c90|
There is a Job ID on some types of log entries, but most don't have it, which means it isn't really suitable for this purpose.
Customer support service by UserEcho