OpenTelemetry Distributed Tracing - APM Instrumentation
Instrument your applications with OpenTelemetry SDKs for distributed tracing and application performance monitoring (APM).
Prerequisites
- An OpenObserve instance (Cloud or self-hosted) and your login credentials.
Trace ingestion endpoint
Configure your OpenTelemetry SDK or Collector to send traces to:
https://<your-openobserve-host>/api/<your-org>/v1/tracesFor self-hosted instances on the default port, this is http://localhost:5080/api/<your-org>/v1/traces. Send the Authorization: Basic <base64(email:password)> header on each request.
SDK examples
You can find examples of how to instrument your code to send traces to OpenObserve using OpenTelemetry SDKs below:
Prefer not to change code? Use OBI (eBPF zero-code instrumentation) to capture traces and metrics automatically, with no SDK.
You can also follow the OpenTelemetry documentation for more info.
Next steps
- OpenTelemetry Collector / OTLP: unified ingestion for logs, metrics, and traces.
- Ingestion overview: all ingestion paths for logs, metrics, and traces.
Need some help?
- Join our Community Slack
- Or Contact support
Last updated on
Index
Configure OpenTelemetry distributed tracing over HTTP or gRPC with OpenObserve for application performance monitoring and microservices observability.
OBI (eBPF zero-code)
Capture application traces and RED metrics without changing code using OpenTelemetry eBPF Instrumentation (OBI) and export them to OpenObserve over OTLP/HTTP.