OpsRamp Distributed Tracing follows requests across services and presents the resulting traces, spans, dependencies, errors, and performance signals in one observability workflow. It supports OpenTelemetry-based instrumentation and multiple collection models so teams can adopt tracing without tying application code to a proprietary telemetry format.

Use this documentation set to understand:

• How traces and spans represent distributed work.
• How context connects operations across process and service boundaries.
• How applications send trace data to OpsRamp.
• Where sampling, ingestion, storage, query, and retention occur.
• Which instrumentation and deployment options are supported.
• Which entitlements and permissions control access.

Documentation map

1. What is Distributed Tracing explains the underlying observability model.
2. Why Tracing in OpsRamp describes the operational value and product workflows.
3. Key Concepts and Terminology defines the data model and lifecycle.
4. How OpsRamp Tracing Works describes architecture, data flow, and deployment models.
5. Supported Languages, Frameworks and Libraries explains instrumentation choices.
6. Support Matrix provides a concise compatibility reference.
7. Data Retention, Limits and Quotas documents data-governance controls.
8. Permissions and Roles explains access requirements.