Migrating to OpenTelemetry
When migrating your services from Honeycomb OpenTelemetry Distribution to OpenTelemetry, automatic instrumentation should not be affected (as long as you install and configure the same instrumentation libraries), and any custom, or manual, instrumentation should not require changes. At a high level, this migration will require that you:Replace Honeycomb OpenTelemetry Distribution packages in your instrumentation with official OpenTelemetry packages.
Visit the “Acquire Dependencies” section of our OpenTelemetry documentation for your coding language, and if needed, update the packages listed therein:
Add direct dependencies for any instrumentation libraries that the Honeycomb OpenTelemetry Distribution included and set up during application initialization.
Visit the “Initialize” section of our OpenTelemetry documentation for your coding language, and if needed, update the packages listed therein:
- OpenTelemetry for Node.js: Initialize
- OpenTelemetry for Go: Initialize
- OpenTelemetry for Python - not required
- OpenTelemetry for Java - not required
- OpenTelemetry for .NET: Initialize
If applicable, add direct dependencies for the baggage span processor.
Visit the “Add Multi-Span Attributes” section of our OpenTelemetry documentation:
If applicable, add the resource attribute for sample rate.
In your Honeycomb OpenTelemetry Distribution, sample rate could have been set with a
SAMPLE_RATE environment variable or as a sampleRate variable in code during initialization.To learn more about adding the Sample Rate resource attribute, visit the “Sampling” section in our OpenTelemetry documentation: