Status: Stable for the trace, metric and log signals. Development for the profiles signal. The OpenTelemetry Protocol (OTLP) specification describes the encoding, transport, and delivery mechanism of telemetry data between telemetry sources, intermediate nodes such as collectors and telemetry backends. OTLP is a general-purpose telemetry data delivery protocol designed in the scope of the OpenTelemetry project. Protocol Details OTLP defines the encoding of telemetry data and the protocol used...| OpenTelemetry
This year marked many milestones for the OpenTelemetry project. The project achieved the goals it had set in 2019 by announcing the general availability of of the logging signal, the last of the signals it had originally committed to. In addition, the project continued to grow the number of contributors, being the second most active project in the CNCF for a second year in a row, behind Kubernetes.| OpenTelemetry
The OpenTelemetry Demo has been updated to version 1.6, and introduces alpha support for the OpenTelemetry Log signal! Our thoughts on logs Why are we considering logging support to be in alpha? There are a few reasons. The most important is that this is the first time we’ve shipped the demo with a logging database. We chose OpenSearch as the storage backend for logs because it’s a popular option that aligns with the project’s license. It’s worth noting that the demo doesn’t require...| OpenTelemetry
The Instrumentation scope represents a logical unit within the application code with which the emitted telemetry can be associated. Developers can decide what denotes a reasonable instrumentation scope. For example, they can select a module, a package, or a class as the instrumentation scope. In the case of a library or framework, a common approach is to use an identifier as scope that is unique to the library or framework, such as a fully qualified name and version of the library or framewor...| OpenTelemetry
Introduction A resource represents the entity producing telemetry as resource attributes. For example, a process producing telemetry that is running in a container on Kubernetes has a process name, a pod name, a namespace, and possibly a deployment name. All four of these attributes can be included in the resource. In your observability backend, you can use resource information to better investigate interesting behavior. For example, if your trace or metrics data indicate latency in your syst...| OpenTelemetry