4 ms·
it's as if we should do logging modeling. There's structure to map logging to the code (sub)processes and also a need to relate traces to lifecycle.
by agumonkey 6y ago
it's as if we should do logging modeling. There's structure to map logging to the code (sub)processes and also a need to relate traces to lifecycle.
- wsargent 6y agoThis is what Honeycomb and Charity Majors talk about when they get into observability. They talk about events rather than logs, and discuss how to construct a meaningful event from a series of data points [1]. Having a good dictionary of logging fields is something that is coming together more [2] although some companies will prevalidate log messages to ensure they meet the given conditions, like Palentir's Witchcraft [3] [1] https://www.honeycomb.io/blog/event-foo-a-series-of-unfortunate-incredible-events/ https://www.honeycomb.io/blog/event-foo-a-series-of-unfortun... [2] https://github.com/vektra/logging-fields https://github.com/vektra/logging-fields [3] https://github.com/palantir/safe-logging https://github.com/palantir/safe-logging
- agumonkey 6y agothanks, very interesting