semantic-conventions/model
Pablo Baeyens 0af7e0efee
[resource/host] Add semantic convention for IP addresses of a host (#203)
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-10-09 07:28:44 +02:00
..
deprecated Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
logs Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
metrics Improve HTTP metric briefs (#366) 2023-10-06 14:29:07 +02:00
resource [resource/host] Add semantic convention for IP addresses of a host (#203) 2023-10-09 07:28:44 +02:00
scope/exporter Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
trace Moved template attributes to yaml model files (#315) 2023-09-26 09:55:47 +02:00
README.md Editorial: Update build-tools to 0.22.0 and sort attributes alphabetically in all semconv (#359) 2023-10-03 09:37:56 +02:00
client.yaml Update client address to be consistent with server address (#302) 2023-09-12 18:01:35 +02:00
destination.yaml Update destination attribute briefs (#243) 2023-08-10 09:56:09 -07:00
error.yaml Introduce request error type attribute (#205) 2023-09-11 17:37:09 +02: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 Move non-`network.*` attributes out of network.yaml (#296) 2023-09-22 18:55:56 +02:00
http-common.yaml Improve `error.type` wording in HTTP semconv (#331) 2023-09-20 18:49:31 +02:00
network.yaml Improve network briefs (#352) 2023-10-02 17:57:37 +02:00
server.yaml Improve symmetry in client/server address/port text (#244) 2023-08-14 12:02:04 -04:00
session.yaml Session.id semantic convention (#215) 2023-09-22 09:04:05 +02:00
source.yaml Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
url.yaml Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07:00
user-agent.yaml Renamed `specification` and `semantic_conventions` to `model` and `docs` (#166) 2023-07-06 11:43:47 -07: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: