OpsRamp accepts traces produced by manually configured OpenTelemetry SDKs. Parameter names differ by language, but each setup needs the same functional values.
| Language | SDK Configuration Area | Required Functional Values |
|---|---|---|
| C++ | SDK resource, provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| .NET | Resource builder, tracer provider, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Erlang | Application environment for SDK and exporter | Service name, endpoint, protocol, authentication, TLS |
| Go | Resource, tracer provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Java | SDK resource, tracer provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| JavaScript | Resource, provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| PHP | SDK resource, provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Python | Resource, tracer provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Ruby | Resource, tracer provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Rust | Resource, provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
| Swift | Resource, provider, processor, OTLP exporter | Service name, endpoint, protocol, authentication, TLS |
Optional settings include batch size, export interval, timeout, propagation, and sampling. Use the exact parameter names documented by the selected OpenTelemetry SDK version. Store credentials in the deployment’s secret-management facility, not application source.