History

Johannes Tax 4204c02ef0 BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948 )		2024-05-03 06:59:02 -07:00
..
logs	Update the device.app.lifecycle event description and constraints (#794 )	2024-04-22 09:41:54 -07:00
metrics	Rename `db.client.connections.` metrics to `db.client.connection.` and rename `db.client.connection.usage` to `db.client.connection.count` and adapting units (#966 )	2024-05-02 11:20:27 -07:00
registry	BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948 )	2024-05-03 06:59:02 -07:00
resource	feat: add k8s.container.status.last_terminated_reason resource attribute (#968 )	2024-04-29 19:58:35 -07:00
scope/exporter	Move otel.scope attributes to registry (#889 )	2024-04-05 14:56:30 +02:00
trace	BREAKING: Rename `messaging.client_id` to `messaging.client.id` (#948 )	2024-05-03 06:59:02 -07:00
README.md	Update build-tools to 0.24.0 (#820 )	2024-03-28 13:05:32 -07:00
db-common.yaml	Remove `db.instance.id` (#972 )	2024-05-01 09:33:31 -07:00
faas-common.yaml	move faas to registry (#525 )	2024-03-07 09:04:52 -08:00
general.yaml	[chore] Add registry prefix to registry namespaces that missing it (#851 )	2024-04-03 13:58:09 +02:00
http-common.yaml	Change `network.protocol.name` from opt-in to conditionally required (#478 )	2023-11-01 09:04:51 +01:00
messaging-common.yaml	Add `messaging.destination.partition.id` to metric attributes (#814 )	2024-04-04 12:20:42 -07:00
network.yaml	Moved network attributes to the registry (#390 )	2023-10-19 14:16:04 +02:00
session.yaml	[chore] Move Session to registry (#843 )	2024-04-03 14:07:31 +02:00
url.yaml	Move url to the registry (#400 )	2023-10-18 12:59:44 +02:00
version.properties	Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166 )	2023-07-06 11:43:47 -07:00

README.md

YAML Model for Semantic Conventions

The YAML descriptions of semantic convention contained in this directory are intended to be used by the various OpenTelemetry language implementations to aid in automatic generation of semantics-related code.

⚠ If you want to read the semantic conventions and not edit them, please see the generated markdown output in the docs folder.

Writing semantic conventions

Semantic conventions for the spec MUST adhere to the attribute naming, attribute requirement level, and metric requirement level conventions.

Refer to the syntax for how to write the YAML files for semantic conventions and what the YAML properties mean.

A schema file for VS code is configured in the /.vscode/settings.json of this repository, enabling auto-completion and additional checks. Refer to the generator README for what extension you need.

Generating markdown

These YAML files are used by the make target table-generation to generate consistently formatted Markdown tables for all semantic conventions in the specification. Run it from the root of this repository using the command

make table-generation

For more information, see the semantic convention generator in the OpenTelemetry build tools repository. Using this build tool, it is also possible to generate code for use in OpenTelemetry language projects.