semantic-conventions/semantic_conventions
Alexander Wert 86dacb9a62
Moved database semantic conventions (#144)
2023-07-01 07:27:27 -07:00
..
deprecated BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` (#3355) 2023-05-08 19:55:53 -07:00
logs Add YAML definitions for log semantic conventions and define requirement levels (#133) 2023-06-30 12:13:12 +02:00
metrics Moved HTTP semantic conventions to a dedicated topic-based structure (#141) 2023-06-28 08:14:15 -07:00
resource Moved general semantic conventions markdown to a topic folder. (#143) 2023-06-30 09:20:14 -07:00
scope/exporter Define semantic conventions yaml for non-otlp conventions (#2850) 2022-10-25 08:46:06 -07:00
trace Moved database semantic conventions (#144) 2023-07-01 07:27:27 -07:00
README.md Moved general semantic conventions markdown to a topic folder. (#143) 2023-06-30 09:20:14 -07:00
client.yaml BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) (#3402) 2023-05-08 16:19:51 -07:00
destination.yaml BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) (#3402) 2023-05-08 16:19:51 -07:00
exception.yaml Suggest column # as an extra source code attribute (#3029) 2023-01-02 18:01:32 -06:00
http-common.yaml Moved HTTP semantic conventions to a dedicated topic-based structure (#141) 2023-06-28 08:14:15 -07:00
server.yaml Recommend emitting server.socket.domain only if it's different from s… (#94) 2023-06-14 20:44:04 -07:00
source.yaml BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) (#3402) 2023-05-08 16:19:51 -07:00
url.yaml BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` (#3355) 2023-05-08 19:55:53 -07:00
user-agent.yaml Rename http.user_agent to user_agent.original (#3190) 2023-03-02 14:47:29 -06:00
version.properties YAML Model for Semantic Conventions (#571) 2020-08-27 13:18:51 -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 specification 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.

See also: