open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
semantic-conventions/semantic_conventions
History
Christian Neumüller 07721f339c Add back refs to cloud.resource_id lost in FaaS renaming. (#3329) 
These places were removed when #3188 in its original form removed
faas.id without replacement and weren't added back after changing it to
introduce cloud.resource_id instead.

Editorial change, no CHANGELOG or issue.
 		2023-04-11 07:13:14 -06:00
..
logs Add semantic conventions for log record ID (#3047) 2023-04-06 13:14:26 -04:00
metrics BREAKING: Remove http.status_code attribute from the http.server.active_requests metric (#3366) 2023-04-06 21:36:41 -07:00
resource Add back refs to cloud.resource_id lost in FaaS renaming. (#3329) 2023-04-11 07:13:14 -06:00
scope/exporter Define semantic conventions yaml for non-otlp conventions (#2850) 2022-10-25 08:46:06 -07:00
trace Change `db.statement` to only be collected if there is sanitization (#3127) 2023-04-06 10:35:33 -07:00
README.md Rename Optional attribute requirement level to Opt-In (#3228) 2023-03-01 15:13:24 -08:00
exception.yaml Suggest column # as an extra source code attribute (#3029) 2023-01-02 18:01:32 -06:00
http-common.yaml BREAKING rename `net.app.protocol.(name|version)` to `net.protocol.(name|version)` and replace `http.flavor` with `net.protocol.(name|version)` (#3272) 2023-03-10 10:15:15 -08: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 under /specification/*/semantic_conventions/, i.e.:

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: