Validate the complete path from application SDK to OpsRamp before production rollout.
| Area | Compatibility Rule |
|---|---|
| Languages | Manual OpenTelemetry SDK paths are documented for C++, .NET, Erlang, Go, Java, JavaScript, PHP, Python, Ruby, Rust, and Swift. |
| Frameworks | Compatibility follows the selected upstream SDK and instrumentation packages. |
| Transport | Use the OTLP/gRPC or OTLP/HTTP endpoint supported by the selected deployment path. |
| Propagation | W3C Trace Context is preferred; configure legacy formats only when required by an existing boundary. |
| Collector | Match exporter, receiver, authentication, and TLS capabilities across versions. |
| Semantic Conventions | Keep one compatible convention set across a service rollout. |
| OpsRamp Features | Widgets, APIs, fields, and limits can vary by release and enabled capability. |
Record application runtime, SDK, exporter, collector, propagator, protocol, and OpsRamp release as one tested combination. A component being supported individually does not prove that an untested combination is compatible. Consult current release notes and retest after changing any element.