2ef85e6e84
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com> Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com> |
||
|---|---|---|
| .. | ||
| cloud-providers | ||
| cloudevents | ||
| database | ||
| exceptions | ||
| faas | ||
| feature-flags | ||
| general | ||
| http | ||
| jvm | ||
| messaging | ||
| object-stores | ||
| resource | ||
| rpc | ||
| system | ||
| url | ||
| README.md | ||
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.
- 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: