APM instrumentation

Instrument with OpenTelemetry

To use Observe APM, you’ll need to instrument your application code with OpenTelemetry. Observe provides documentation on how to add OpenTelemetry instrumentation for the following languages and runtimes:

java.html

dotnet.html

nodejs.html

python.html

ruby.html

For other languages, you can use the OpenTelemetry documentation for how to instrument your application code:

https://opentelemetry.io/docs/languages/cpp/getting-started/

https://opentelemetry.io/docs/languages/erlang/getting-started/

https://opentelemetry.io/docs/languages/go/getting-started/

https://opentelemetry.io/docs/languages/php/getting-started/

https://opentelemetry.io/docs/languages/rust/getting-started/

My applications are already instrumented with OpenTelemetry

See how to point your OTLP exporter to Observe.

Runtime metrics

In order to view runtime metrics for your services in Observe APM, you will need to set the metric temporality to delta. This can be configured using the standard OTel environment variable OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta. The runtime metrics will also need to be sent to Observe as OTel metrics and not Prometheus metrics. If you are running the observe-agent on a host or containerized environment, ensure that the following option is set: forwarding.metrics.output_format: otel. If you are running the observe-agent in kubernetes, then ensure that node.forwarder.metrics.outputFormat=otel is set in your values.yaml file when installing or upgrading the observe-agent helm chart.

To associate your infra metrics with your services and display them alongside runtime metrics in APM, see Associate Infrastructure Metrics with Services.