Use this guide when an instrumented function or managed application exports OTLP from a serverless runtime.

Check the runtime constraints

Before configuring export, confirm that the provider and runtime allow the required outbound network path to an OpsRamp-supported endpoint, Collector, or trace proxy. Check whether the function can reach the configured host and port, whether private networking is required, and how much time the runtime allows for export during shutdown.

Configure the SDK

Add and configure the OpenTelemetry SDK supported by the application’s language and runtime. Set a stable service name and configure OTLP endpoint, protocol, TLS, and authentication using the tenant’s Trace Setup instructions. Prefer OTLP/HTTP when the selected SDK or network path does not support gRPC.

Store client secrets in the provider’s managed secret facility and grant access only to the function identity. Do not package credentials in the deployment artifact or write them to logs.

Account for invocation lifecycle

Use an SDK/exporter configuration compatible with the provider’s execution model. Ensure spans are exported before the invocation or instance is stopped, within the provider’s execution limits. If the runtime cannot reliably reach the endpoint or complete exports, use a Collector or gateway architecture supported by the platform team.

Verify

Invoke a representative request and check the function’s exporter and network logs. Then follow Verify Trace Ingestion to confirm the trace appears in OpsRamp.