Skip to main content
min read

Standardize telemetry names before buying another dashboard_

OpenTelemetry semantic conventions provide common names across traces, metrics, logs, profiles, and resources. That standardization is mundane—and exactly why it makes cross-service diagnosis possible.

  • OpenTelemetry
  • Telemetry
  • Platform Engineering

OpenTelemetry semantic conventions provide common names across traces, metrics, logs, profiles, and resources. That standardization is mundane—and exactly why it makes cross-service diagnosis possible.

When each team names the same request, database, or error differently, dashboards become translation projects. A new observability vendor does not repair inconsistent instrumentation.

What changes in practice_

Adopt a small supported attribute set, review cardinality, and make instrumentation part of service templates and code review.

  • Prefer common attributes over local inventions.
  • Control high-cardinality values.
  • Version conventions as the organization changes.

Our take_

The durable advantage is not adopting the newest tool first. It is building the identity, state, evidence, and operating boundaries that let a real team own the system after launch.

Source_

Our take - not a reprint. Read the original for full reporting.

Want this applied to your stack?

Map your systems or book discovery - we keep humans accountable for what ships.