OpsRamp tracing connects application telemetry with request investigation, service performance, and trace-volume management. Applications use standard OpenTelemetry instrumentation and export through the collection path selected for their deployment.
At a high level:

1. Applications create spans through OpenTelemetry SDKs and supported instrumentation libraries.
2. Spans are exported to the OpsRamp trace proxy, optionally through an OpenTelemetry Collector.
3. The trace proxy uses the OpsRamp endpoint, authentication settings, and client context supplied for the deployment.
4. Authorized users search traces, inspect spans, and compare service and operation performance in OpsRamp.
5. Administrators review ingestion usage, sampling, and retention to manage trace volume and availability.

The pages in this section describe:

• Tracing Architecture: collection choices and the trace investigation workflow;
• Data Flow: Application to OpsRamp: how application spans reach the trace views; and
• Trace Proxy Deployment Models: application-to-proxy and Collector-to-proxy layouts.

Select the intended client before opening trace views. Trace Monitoring must be enabled for that client, and your role must provide the appropriate tracing permissions.