Structured logging means emitting log lines as machine-parseable records rather than free-form text strings. Instead of logging 'GET /live_score 200 23ms', structured logging emits a JSON object with separate fields for method, path, status_code, and duration_ms. This distinction matters because free-form logs require pattern matching at query time (regex-based parsing that is slow and fragile), while structured logs enable direct field access, numeric comparisons, and reliable aggregation. Loki's json() and logfmt() parsers extract structured fields at query time, enabling LogQL expressions like duration_ms > 500 without per-application Loki pipeline configuration.
Analogy🏏Cricket
🏏 Think of it like cricket: During India's 2023 World Cup final against Australia, the team management tracked three distinct data streams simultaneously to understand match performance. The scoreboard showed run rate, current score, and required run rate — aggregated numbers updated every over, equivalent to metrics. The commentary and match notes recorded each delivery's outcome — Rohit Sharma edged a yorker from Hazlewood at the 12th over, first ball — equivalent to logs. The ball-tracking DRS system traced the exact path of each delivery from Bumrah's hand through the air to the stumps, showing the full journey of that dismissal — equivalent to traces. Just as the scoreboard alone cannot explain why the run rate collapsed (you need the logs to see specific wicket events and traces to follow the pressure chain from bowler to batter to fielder), metrics alone cannot explain why your API latency spiked — you need logs for individual request events and traces to follow the request across services. The insight is that each pillar answers a different question: metrics give magnitude, logs give events, and traces give causality — and you need all three to diagnose a complex failure.