Status: Development A Schema File is a YAML file that describes the schema of a particular version. It defines the transformations that can be used to convert the telemetry data represented in any other older compatible version of the same schema family to this schema version. File Structure Here is the structure of the Schema File: # Defines the file format. MUST be set to 1.1.0. file_format: 1.1.0 # The Schema URL that this file is published at. The version number in the URL # MUST match th...| OpenTelemetry
Status: Development A Schema File is a YAML file that describes the schema of a particular version. It defines the transformations that can be used to convert the telemetry data represented in any other older compatible version of the same schema family to this schema version. File Structure Here is the structure of the Schema File: # Defines the file format. MUST be set to 1.0.0. file_format: 1.0.0 # The Schema URL that this file is published at. The version number in the URL # MUST match th...| OpenTelemetry
Contents Overview Glossary Principles and Guidelines Core Principles Versioning and stability for OpenTelemetry clients Library Guidelines Package/Library Layout General error handling guidelines Performance API Specification Context Propagators Environment Variable Carriers Baggage Tracing Metrics Logs API SDK Specification Tracing Metrics Logs Resource Configuration Data Specification Semantic Conventions Protocol Metrics Logs Profiles Compatibility OpenCensus OpenTracing Prometheus and Ope...| OpenTelemetry
Status: Stable, except where otherwise specified Overview The Metrics API consists of these main components: MeterProvider is the entry point of the API. It provides access to Meters. Meter is responsible for creating Instruments. Instrument is responsible for reporting Measurements. Here is an example of the object hierarchy inside a process instrumented with the metrics API: +-- MeterProvider(default) | +-- Meter(name='io.opentelemetry.runtime', version='1.0.0') | | | +-- Instrument(name='c...| OpenTelemetry
Specification documents (files) may explicitly define a “Status”, typically shown immediately after the document title. When present, the “Status” applies to the individual document only and not to the entire specification or any other documents. The following table describes what the statuses mean. Maturity levels The support guarantees and allowed changes are governed by the maturity level of the document. Maturity levels are defined in OTEP 0232 and follow the OpenTelemetry project...| OpenTelemetry
Status: Stable, except where otherwise specified The Tracing API consists of these main components: TracerProvider is the entry point of the API. It provides access to Tracers. Tracer is responsible for creating Spans. Span is the API to trace an operation. Data types While languages and platforms have different ways of representing data, this section defines some generic requirements for this API. Time OpenTelemetry can operate on time values up to nanosecond (ns) precision. The representati...| OpenTelemetry