All insights
DevOps6 min read
Consistent service telemetry with OpenTelemetry conventions
A practical way to standardise names and attributes before dashboards and alerts become difficult to trust.
Shared meaning reduces operational friction
OpenTelemetry semantic conventions define common names and attributes for telemetry. Adopting a stable subset helps teams correlate signals across services and prevents every dashboard from inventing a different vocabulary.
Start from operational questions
List the questions responders must answer: which service is affected, what operation is failing, which dependency is involved, and whether a release changed behaviour. Then map those questions to consistent resource and span attributes.
- Document required attributes.
- Avoid sensitive or high-cardinality values.
- Validate telemetry in delivery checks.
- Review convention changes during upgrades.
Treat conventions as an interface
Dashboards, alerts, and investigations depend on emitted names. Manage changes deliberately, keep a compatibility plan, and test that core telemetry remains present after deployment.