Configure OBI export modes
Configure OBI to export data directly to an OTLP endpoint
You are viewing the English version of this page because it has not yet been fully translated. Interested in helping out? See Contributing.
You can configure OBI by setting export modes, global properties, and component options.
For information on the metrics OBI exports, refer to the exported metrics documentation.
Refer to the routes decorator documentation to configure the low cardinality routes decorator. It’s very important for optimal results.
Use Config v2 with OBI v0.11.0 and later. It works with standalone OBI and the
OBI Collector receiver, uses the OpenTelemetry declarative configuration
structure for common settings, and places OBI-specific settings under
extensions.obi.
Unless otherwise noted, the other pages in this section describe Config v1. Each page links to the corresponding Config v2 guidance.
Configure OBI to export data directly to an OTLP endpoint
Configure global configuration properties that apply to OBI core.
Learn how to configure standalone OBI or the OBI Collector receiver with Config v2.
Learn how to safely migrate an OBI Config v1 file to Config v2.
Configure the OBI components to export Prometheus and OpenTelemetry metrics and OpenTelemetry traces
Configure how the OBI service discovery component searches for processes to instrument.
Configure the metrics and traces attributes component that controls the attributes reported, including instance ID decoration and metadata of instrumented Kubernetes pods.
Configure OBI to filter metrics and traces by attribute values.
Configure the routes decorator component before OBI sends data to the next stage of the pipeline.
Configure metrics histograms for Prometheus and OpenTelemetry, and whether to use native histograms and exponential histograms.
Configure how to sample OpenTelemetry traces.
Learn how to use OBI as a receiver component in the OpenTelemetry Collector for centralized telemetry processing.
Configure how the optional internal metrics reporter component reports metrics on the internal behavior of the auto-instrumentation tool in Prometheus format.
Configure how the eBPF tracer component instruments HTTP and GRPC services of external processes and creates traces to forward to the next stage of the pipeline.
Example Config v1 YAML file for OBI.
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!