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/docs
History
Liudmila Molkova 06b0b624a4
Deprecate `tls.client.server_name` attribute in favor of common `server.address` (#1216) 
Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com>
 		2024-07-22 15:07:23 +00:00
..
attributes-registry Deprecate `tls.client.server_name` attribute in favor of common `server.address` (#1216) 2024-07-22 15:07:23 +00:00
cloud-providers [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
cloudevents CloudEvents should re-use existing HTTP or messaging conventions (#1182) 2024-07-16 07:13:08 +00:00
database db.query.text IN-clauses MAY be collapsed during the sanitization process (#1243) 2024-07-15 16:17:06 -07:00
dns [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
dotnet Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00
exceptions [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
faas Revamp messaging metrics to support generic operations (#1006) 2024-06-14 14:39:47 -07:00
feature-flags [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
gen-ai Convert `gen_ai.operation.name` to enum and use it on spans (#1202) 2024-07-09 17:33:49 -07:00
general [chore] Add clarification on event attributes vs body fields (#1263) 2024-07-22 15:05:50 +00:00
graphql [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
http Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00
messaging Deprecate `messaging.destination_publish.*` namespace and remove all usages (#1241) 2024-07-15 11:40:23 -07:00
mobile [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
object-stores [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
resource [cicd] add initial cicd attributes to registry (#1075) 2024-07-19 14:29:37 +02:00
rpc Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00
runtime Add v8 js engine runtime metrics semantic conventions (#1066) 2024-07-08 07:25:55 -07:00
system Add QUIC to the list of well known network transports (#1239) 2024-07-15 09:04:16 -07:00
url [chore] Use document status link to otel.io instead of versioned spec (#1093) 2024-06-03 13:33:39 +02:00
README.md LLM Semantic Conventions: Initial PR (#825) 2024-04-16 16:04:32 -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:

  • 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.
  • Generative AI: Semantic Conventions for generative AI (LLM, etc.) operations.
  • 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.