Upgrade one controlled group at a time and validate trace continuity before broad rollout. Review the library, collector, and OpsRamp compatibility information supplied for the target versions.
Upgrade safely
- Inventory current language libraries, collector versions, exporters, propagators, and endpoint protocols.
- Review release notes for configuration, semantic-convention, and default-behavior changes.
- Back up the current configuration and define rollback criteria.
- Upgrade a non-production or canary deployment.
- Generate representative successful and failed requests.
- Compare trace counts, service and operation names, attributes, errors, propagation, and trace-derived metrics.
- Expand the rollout while monitoring dropped spans and export failures.
Do not change sampling rules, service names, and library versions in the same validation step. Keeping changes separate makes regressions easier to identify. Never place ingestion credentials in source code or upgrade logs.