OpsRamp tracing is built around manual OpenTelemetry instrumentation that exports OTLP. Application teams select the SDKs and instrumentation libraries appropriate for their runtime, then send traces to the OpsRamp trace proxy, optionally through an upstream OpenTelemetry Collector.
Manual and upstream OpenTelemetry instrumentation
OpsRamp documentation provides OpenTelemetry instrumentation paths for:
- C++
- .NET
- Erlang
- Go
- Java
- JavaScript
- PHP
- Python
- Ruby
- Rust
- Swift
For these languages, framework and library coverage follows the instrumentation packages provided by the corresponding OpenTelemetry project. Verify runtime and package compatibility against the OpenTelemetry documentation for the SDK and package versions you deploy.
Frameworks and libraries
Framework and library coverage depends on the OpenTelemetry packages selected for the application. Common categories include HTTP clients and servers, Servlet and WSGI/ASGI frameworks, gRPC, database clients, and messaging libraries such as Kafka.
Framework compatibility can change independently of OpsRamp. Before production rollout, validate the application runtime, framework version, OpenTelemetry instrumentation version, and required semantic attributes in a staging environment.
Protocols
Instrumented workloads can use OTLP/gRPC or OTLP/HTTP to send spans to the trace proxy, optionally through a Collector. Applications and Collectors use the proxy’s application-facing endpoint; the proxy forwards trace data to OpsRamp.