I'll give you an example: we have a stack trace error regularly occurring in the client log that says "field value required" there are no further details before or after. It is likely the result of some external application (Splunk, LogRythym,…) trying to create an incident but I cannot tell.
it would be awesome if there was another level of debugging that could help with this.
It may be possible to correlate by the time stamp if something is happening in the app log at the same time. I'll have to check.
------------------------------
Tim Gray
------------------------------
Original Message:
Sent: Thu August 12, 2021 03:30 PM
From: Liam Mahoney
Subject: enhanced logging for client.log file
Hi Tim,
What kind of additional information are you looking for? I'm thinking there might be an additional log that would contain the information you want.
------------------------------
Liam Mahoney
Original Message:
Sent: Thu August 12, 2021 01:55 PM
From: Tim Gray
Subject: enhanced logging for client.log file
Hello,
I have debug enabled in the app.config, but I would like to enable further logging that occurs in the /usr/share/co3/log/client.log file.
Is there another place to enable debugging resilient output?
------------------------------
Tim Gray
------------------------------