Introduction: The Tower of Babel Problem

The Chaos of Naming

Imagine you are debugging an outage. You open your logging tool and search for errors from your checkout service.

• Query 1: app_name="checkout" → No results.
• Query 2: service="checkout-api" → No results.
• Query 3: application="CheckoutService" → Found it!

Now you want to see the metrics for that service. You switch to your dashboard tool.

• Query: application="CheckoutService" → No results.
• Reason: The metrics team decided to use job_name instead of application.

This is the Tower of Babel problem. Every team names things differently, so you cannot correlate data across signals. You cannot jump from a log to a trace to a metric because the keys don't match. During an outage, this naming chaos costs you minutes — sometimes tens of minutes — of manual detective work before you even start solving the actual problem.

Semantic Conventions are the solution. They are the official, versioned dictionary published by the OpenTelemetry project that dictates exactly what attributes should be called, what type they must be, and what values are valid.