Source: medium.com
Redesigning Observability Logging
Does the software industry need yet another logging library? Before listing various issues with today’s logging, let’s recap what it looks like for the average enterprise developer when it comes to instrumentation.
Again this stems from yesteryear thinking of record-based logging— ignorant of the unfolding situation and not assessing the importance of a record in light of the state of the environment and context.
Logging and eventing need to move away from a singular focus on records to one that encompasses sequencing of records, nesting of entity and execution contexts, as well as the state of the environment.
The Name used to create the Emitter is the event type and the Environment the state of the event, including the enclosing context.
Again this stems from yesteryear thinking of record-based logging— ignorant of the unfolding situation and not assessing the importance of a record in light of the state of the environment and context.
Logging and eventing need to move away from a singular focus on records to one that encompasses sequencing of records, nesting of entity and execution contexts, as well as the state of the environment.
The Name used to create the Emitter is the event type and the Environment the state of the event, including the enclosing context.
Related Articles
Community Partners
DevOps Careers