Overview
Odigos will automatically apply instrumentation to your selected workloads to record observability signals from your services such as collecting traces, metrics, and logs without any code changes.
Supported Runtimes
Odigos provides automatic instrumentations for the following runtimes:
Go
Javascript
Python
Java
.NET
PHP
Enrich with OpenTelemetry APIs
Odigos automatically generates data for open-source libraries and frameworks. Additional trace spans, metrics datapoints and log records can be added using the OpenTelemetry APIs. Odigos will automatically capture this data and deliver it to the chosen destination alongside the automatically generated data.
No need to configure the OpenTelemetry SDK, Odigos will automatically configure it for you.
Select a language to learn how to enrich your data with OpenTelemetry APIs:
Go
Javascript
Python
Java
.NET
PHP
Instrumentation Flow:
- User selects a workload to auto instrument by creating a
Source
object (per workload or per namespace). - Odigos
instrumentor
component watches for changes withSource
objects, and creates a relativeInstrumentationConfig
object. - Odigos
odiglet
component watches for changes with theInstrumentationConfig
objects, and runs a runtime inspection on running pods to detect the programming language for every container. - Odigos
instrumentor
component watches for changes with theInstrumentationConfig
object, and adds a resource request into each pod spec of all relevant containers in the workload manifest. These resource requests are calledInstrumentation Devices
. - Kubernetes detects the changes in the manifest, and rollout-restarts the pods with the new
Instrumentation Devices
. - New pods are scheduled and started. Odiglet resolves the resource request by mounting the auto instrumentation code and relevant environment variables into the container.
- The auto instrumentation code starts the OpenTelemetry SDK and sends telemetry data to the odigos pipeline.
In case of a failure to instrument a workload, Odigos will disable the instrumentation and rollback the workload, This behaviour can be disabled by running bash odigos config set rollback-disabled true
or via the helm chart autoRollback.disabled=false