Examples of blessed information that I have seen in the context of logging:
Stacktraces logged by a library that elide all the superfluous parts of the stacktraces.
A log message that says exactly what the problem is, why it is caused (e.g., which parameters lead to it), and where to find more information about it (ticket number, documentation page).
The presence of a Correlation IDs (also called Transaction ID, Request ID, Session ID, Trace ID).
What is a correlation ID? It is an ID that is created at the start of a request/session and available in all logs related to that request/session. See here or here, implementations here or here. There are even hierarchical correlation IDs
Esp. useful: A correlation ID that is accessible from the client.
Even more useful: If there is a single place to search all the logs of a system for the ID.
Aggregation of logs, such that only the first, ten’s, 100s… of a log message is escalated.
Examples of blessed information that I have seen in the context of logging:
Stacktraces logged by a library that elide all the superfluous parts of the stacktraces.
A log message that says exactly what the problem is, why it is caused (e.g., which parameters lead to it), and where to find more information about it (ticket number, documentation page).
The presence of a Correlation IDs (also called Transaction ID, Request ID, Session ID, Trace ID).
What is a correlation ID? It is an ID that is created at the start of a request/session and available in all logs related to that request/session. See here or here, implementations here or here. There are even hierarchical correlation IDs
Esp. useful: A correlation ID that is accessible from the client.
Even more useful: If there is a single place to search all the logs of a system for the ID.
Aggregation of logs, such that only the first, ten’s, 100s… of a log message is escalated.