What is logging, in one word? Cost. Undeniably.
Development cost. Performance cost. Operational cost. Maintenance cost.

But is logging truly costly, or merely expensive?
As with education, the answer depends on outcomes, and those outcomes only become visible over time.

By approaching logging the way we approach learning, we can transform a controversial expense into an operational necessity.
We employ a discreet but continuous source of insight across business, development, architecture and design, security, and incident response.

When designed intentionally, logs tell stories about both system and human behaviors.
They reveal how our services actually run and where assumptions quietly fail.
In that sense, observability through logging is not a sunk cost, but a high-return investment in understanding and decision-making, potentially offering a multi-aspect business intelligence solution.

In this talk, we explore how to extract real value from logging by mapping it to three universal dimensions of learning:
-Things we know that we know
-Things we know that we do not know
-Things we do not know that we do not know