Semantic conventions define standard span names and attribute keys for common protocols, resources, and operations. Consistent conventions make searches, topology, metrics, and cross-team dashboards reusable.

Apply conventions

1. Set a stable service.name resource attribute.
2. Select the convention matching the operation, such as HTTP, RPC, database, messaging, or a Kubernetes resource.
3. Use stable route or operation templates rather than raw identifiers.
4. Record errors with span status and the convention’s approved error attributes.
5. Validate attribute names against the OpenTelemetry semantic-convention version used by the deployed library.

Conventions evolve independently of OpsRamp releases. Do not mix renamed keys across replicas of one service during a rollout. Application-specific attributes should use a documented namespace, bounded values, and no secrets or personal data.

For more information, see OpenTelemetry Semantic Conventions.