What problem does it solve? Honeycomb Beelines have reached End of Life and are archived, so teams must migrate to OpenTelemetry without breaking distributed traces across services that still run mixed instrumentation. ## Core Features & Use Cases - Two-Phase Migration Strategy: Enable W3C trace propagation on all Beeline services first, then migrate services to OpenTelemetry one at a time without breaking trace linking. - Per-Language Migration Guides: Provides before/after code and field mappings for Go, Python, Node.js, Java, and Ruby Beelines. - Safety Checklists: Covers service-name preservation, custom field auditing, and attribute name differences between Beeline and OTel. - Use Case: A platform team running Python and Node.js services on Honeycomb Beelines uses this guide to enable W3C headers everywhere, then incrementally replace each Beeline SDK with OpenTelemetry while keeping traces connected. ## Quick Start Ask the assistant to walk you through migrating your service from Honeycomb Beeline to OpenTelemetry, starting with enabling W3C trace propagation.
