Comment by gijoeyguerra

Persisting a data schema that represents business events is a great idea. That’s more about Event Sourcing though and doing that can answer a ton of questions about the system without doing it in log messages.

Wide events as a strategy is expensive, even with sampling, and doesn’t address the fundamental problem - why do we log messages?

I was hoping the article would enumerate why we log messages. Nailing down those scenarios first will lead to a happy life.

Why do we log? - proof of life - is the system running? - what is the state (in memory) when an error occurred? - when did an error occur? - do I need to get up at 2 am and fix something? - what do I need to fix?

I feel like every team operating a system has their own reasons for logging.