OpsRamp tracing connects instrumented applications to trace investigation and service insights. Choose a collection path that fits your application’s network, security, and telemetry requirements.

Collection layer

• OpenTelemetry SDKs and instrumentation libraries generate OTLP-compatible spans.
• OpenTelemetry Collector can optionally receive, process, batch, and forward spans to the trace proxy.
• OpsRamp trace proxy is the supported trace-ingestion path to OpsRamp. It can buffer spans into complete traces, apply trace-aware sampling, consolidate traffic, and generate trace-derived metrics before forwarding.

Collection paths

Manually instrumented applications export spans to the OpsRamp trace proxy, optionally through an OpenTelemetry Collector.
Use a Collector when you need a central location for SDK egress and telemetry processing before the trace proxy. Configure the application or Collector with the proxy’s application-facing endpoint. Keep the OpsRamp endpoint, authentication, and client settings in the trace proxy’s protected configuration.

Investigate in OpsRamp

After export, use the trace views for the intended client to find requests, inspect span timing and parent-child relationships, and compare service and operation performance. Available attributes, events, and error details depend on what your application records.
Trace Monitoring must be enabled for the client, and users need the appropriate tracing permissions. Sampling determines which traces are forwarded; retention determines how long accepted trace data remains available. Review these settings when planning volume or investigating missing data.