Migrate by preserving open trace context and semantic conventions, then changing the export destination in controlled stages. OpsRamp does not require historical data from another tracing product to be imported before new traces can be observed.
Plan the migration
- Inventory services, manual instrumentation, propagation formats, sampling, attributes, dashboards, alerts, and retention requirements.
- Standardize service and operation names and remove vendor-specific assumptions from application code where practical.
- Configure the application exporter to send spans to the required OpsRamp trace proxy, optionally through an OpenTelemetry Collector.
- Validate a representative service, including cross-service propagation and errors.
- Recreate required dashboards and alerts using verified trace-derived metrics.
- Move services in groups and compare coverage during an agreed overlap period.
- Remove the former export path only after acceptance criteria pass.
Avoid sending duplicate telemetry longer than needed. A bulk migration wizard and universal historical-trace import are not assumed. Confirm any data migration requirement with OpsRamp support before committing to it.