semantic-conventions/specification
Chris Mark afc81230cd
Add YAML definitions for log semantic conventions and define requirement levels (#133)
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-30 12:13:12 +02:00
..
http Moved HTTP semantic conventions to a dedicated topic-based structure (#141) 2023-06-28 08:14:15 -07:00
logs/semantic_conventions Add YAML definitions for log semantic conventions and define requirement levels (#133) 2023-06-30 12:13:12 +02:00
metrics/semantic_conventions JVM cpu metrics opt-in (#57) 2023-06-28 17:26:37 +02:00
resource/semantic_conventions Add container semantic conventions resource (#39) 2023-06-28 11:42:25 -04:00
trace/semantic_conventions Add semantic conventions for Elasticsearch client instrumentation (#23) 2023-06-29 16:05:52 +02:00
README.md Moved HTTP semantic conventions to a dedicated topic-based structure (#141) 2023-06-28 08:14:15 -07:00

README.md

OpenTelemetry Semantic Conventions

The Semantic Conventions define a common set of (semantic) attributes which provide meaning to data when collecting, producing and consuming it. The Semantic Conventions specify among other things span names and kind, metric instruments and units as well as attribute names, types, meaning and valid values. For a detailed definition of the Semantic Conventions' scope see Semantic Conventions Stability. The benefit to using Semantic Conventions is in following a common naming scheme that can be standardized across a codebase, libraries, and platforms. This allows easier correlation and consumption of data.

Semantic Conventions are defined for the following areas:

  • HTTP: Semantic Conventions for HTTP client and server operations.
  • Other areas can be found in the signal specific Semantic Conventions below

Semantic Conventions by signals:

  • Resource: Semantic Conventions for resources.
  • Trace: Semantic Conventions for traces and spans.
  • Metrics: Semantic Conventions for metrics.
  • Logs: Semantic Conventions for logs and event data.