semantic-conventions/model
Patrice Chalin 231ba7b060
[editorial] Use canonical URL to connectrpc.com instead of connect.build (#1933)
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2025-02-25 12:42:54 +00:00
..
android Rework device events (#1880) 2025-02-18 10:04:31 -08:00
artifact Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
aspnetcore Remove requirement_level usages from registry and add a policy to check (#1606) 2024-11-25 11:08:46 -05:00
aws Set span kind on span definitions or change ambiguous spans to attribute groups (#1890) 2025-02-12 10:45:31 -08:00
azure Clarify notes on system-specific databases for operation and collection names (#1863) 2025-02-19 18:38:37 -08:00
browser Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
cassandra Consistent naming: `db.system` to `db.system.name`, namespace constants, remove `db` from system-specific names (#1734) 2025-01-23 23:02:12 -08:00
cicd Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
cli Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
client Group yaml files by root namespace instead of signal (#1345) 2024-09-16 20:22:50 -07:00
cloud Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
cloudevents Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
cloudfoundry Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
code Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
container Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
cpu Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
database Clarify notes on system-specific databases for operation and collection names (#1863) 2025-02-19 18:38:37 -08:00
deployment Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
destination Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
device Rework device events (#1880) 2025-02-18 10:04:31 -08:00
disk Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
dns Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
dotnet Mark .NET runtime metrics as stable (#1609) 2024-12-03 12:39:24 -08:00
elasticsearch Consistent naming: `db.system` to `db.system.name`, namespace constants, remove `db` from system-specific names (#1734) 2025-01-23 23:02:12 -08:00
enduser Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
error [chore] Improve markdown gen for registry pages (#1496) 2024-10-21 07:32:21 -07:00
event/deprecated Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
exceptions Add common guidance on recording errors on spans and metrics, clarify DB conventions (#1716) 2025-01-16 11:54:10 -08:00
faas Set span kind on span definitions or change ambiguous spans to attribute groups (#1890) 2025-02-12 10:45:31 -08:00
feature-flags Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
file Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
gcp Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
gen-ai Update to weaver 0.13.2 (#1902) 2025-02-14 08:26:19 -08:00
geo Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
go Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
graphql Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
hardware Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
heroku Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
host Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
http Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
ios Rework device events (#1880) 2025-02-18 10:04:31 -08:00
jvm Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
k8s Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
kestrel Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
linux Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
log Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
messaging Set span kind on span definitions or change ambiguous spans to attribute groups (#1890) 2025-02-12 10:45:31 -08:00
network Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
nodejs Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
oci Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
opentracing Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
os Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
otel Add SDK span telemetry metrics (#1631) 2025-02-13 09:38:45 +01:00
peer Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
process Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
profile Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
rpc [editorial] Use canonical URL to connectrpc.com instead of connect.build (#1933) 2025-02-25 12:42:54 +00:00
security-rule Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
server Group yaml files by root namespace instead of signal (#1345) 2024-09-16 20:22:50 -07:00
service Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
session Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
signalr Group yaml files by root namespace instead of signal (#1345) 2024-09-16 20:22:50 -07:00
source Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
system Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
telemetry Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
test Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
thread Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
tls Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
url [editorial] Use canonical https URLs (#1934) 2025-02-24 13:33:12 -08:00
user Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
user-agent Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
v8js Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
vcs Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
webengine Update stability levels from experimental -> development (#1889) 2025-02-11 18:06:51 -08:00
README.md [editorial] A few random doc fixes (#1704) 2024-12-27 09:04:58 +01: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.

[!NOTE]

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 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.

When defining semantic conventions, follow contributing guide:

  • If new attributes are necessary, define them in the attribute registry. Attributes can only be defined inside groups with attribute_group type and with id starting with registry. prefix.
  • Define new spans, metrics, events, resources, and other conventions using appropriate group type. See semantic convention groups for more details.

Generating markdown

These YAML files are used by the make targets attribute-registry-generation and 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 attribute-registry-generation table-generation

For more information, see the Weaver as our code generations tool.

Validating semantic conventions

Semantic conventions YAML files are validated by the check-policies make target for backward compatibility, name formatting, and other policies.

You can run it with the following command:

make check-policies

See also: