semantic-conventions/model
Alexander Wert e3da931d08
Add `code.stacktrace` attribute (#435)
Signed-off-by: Alexander Wert <alexander.wert@elastic.co>
2023-11-09 08:17:32 -06:00
..
logs added mobile instrumentation to log-event semantic conventions (#67) 2023-10-20 10:11:52 +02:00
metrics Make url.scheme opt in for HTTP client metrics and make server.port required (#459) 2023-10-31 10:59:22 +01:00
registry Add `code.stacktrace` attribute (#435) 2023-11-09 08:17:32 -06:00
resource docs: explain deployment.environment impact on service identity (#481) 2023-11-07 13:54:51 +01:00
scope/exporter Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
trace Make `user_agent.original` and `http.request.header.*` attributes sampling relevant on HTTP server spans (#467) 2023-11-02 13:47:08 -04:00
README.md Change sampling relevant from MUST to SHOULD (and update build-tools version) (#486) 2023-11-02 16:41:11 +01:00
client.yaml Mark HTTP semantic conventions as stable (#377) 2023-11-03 12:05:54 -04:00
destination.yaml Editorial: random improvements (#415) 2023-10-19 16:53:57 -07:00
error.yaml Mark HTTP semantic conventions as stable (#377) 2023-11-03 12:05:54 -04:00
exception.yaml Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
faas-common.yaml Generate FaaS metrics semconv from YAML (#88) 2023-08-07 08:27:53 -07:00
general.yaml Add `code.stacktrace` attribute (#435) 2023-11-09 08:17:32 -06:00
http-common.yaml Change `network.protocol.name` from opt-in to conditionally required (#478) 2023-11-01 09:04:51 +01:00
network.yaml Moved network attributes to the registry (#390) 2023-10-19 14:16:04 +02:00
server.yaml Mark HTTP semantic conventions as stable (#377) 2023-11-03 12:05:54 -04:00
session.yaml Add session.previous_id (#348) 2023-10-21 15:40:31 +02:00
source.yaml Editorial: random improvements (#415) 2023-10-19 16:53:57 -07: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.

See also: