semantic-conventions/docs
Joao Grassi 1d592b44a7
[chore] Move telemetry sdk to the registry (#873)
2024-04-03 17:16:14 +02:00
..
attributes-registry [chore] Move telemetry sdk to the registry (#873) 2024-04-03 17:16:14 +02:00
cloud-providers Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
cloudevents Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
database [chore] Move Dynamodb attributes to the registry (#850) 2024-04-03 11:20:42 +02:00
dns Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
dotnet Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
exceptions Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
faas Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
feature-flags Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
general [chore] Move Session to registry (#843) 2024-04-03 14:07:31 +02:00
graphql Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
http Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
messaging [chore] Cleanup minor issues in messaging semconv (#859) 2024-04-02 08:32:24 -07:00
mobile Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
object-stores Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
resource [chore] Move telemetry sdk to the registry (#873) 2024-04-03 17:16:14 +02:00
rpc Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
runtime Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
system Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
url Update build-tools to 0.24.0 (#820) 2024-03-28 13:05:32 -07:00
README.md [chore] Move GraphQL out of database folder/semconv (#736) 2024-02-15 19:41:03 +01: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:

  • General: General Semantic Conventions.
  • Cloud Providers: Semantic Conventions for cloud providers libraries.
  • CloudEvents: Semantic Conventions for the CloudEvents specification.
  • Database: Semantic Conventions for database operations.
  • Exceptions: Semantic Conventions for exceptions.
  • FaaS: Semantic Conventions for Function as a Service (FaaS) operations.
  • Feature Flags: Semantic Conventions for feature flag evaluations.
  • GraphQL: Semantic Conventions for GraphQL implementations.
  • HTTP: Semantic Conventions for HTTP client and server operations.
  • Messaging: Semantic Conventions for messaging operations and systems.
  • Object Stores: Semantic Conventions for object stores operations.
  • RPC: Semantic Conventions for RPC client and server operations.
  • System: System Semantic Conventions.

Semantic Conventions by signals:

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