skills.rest
honeycombio
honeycombioOFFICIAL
Explore all skills by this author →
Website𝕏@honeycombioGitHub

beeline-migration

Guide phased migration from Honeycomb Beeline instrumentation to OpenTelemetry SDKs.

20|7|Updated Feb 7, 2026
Search Tags:#migration#observability#instrumentation#opentelemetry#honeycomb#beeline
One-click install
npx skills add https://github.com/honeycombio/agent-skill --skill beeline-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beeline-migration
Source: https://github.com/honeycombio/agent-skill/tree/main/honeycomb/skills/beeline-migration
Command: npx skills add https://github.com/honeycombio/agent-skill --skill beeline-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear, step-by-step process to migrate your Honeycomb Beeline instrumentation to OpenTelemetry, ensuring continued observability as Beelines reach End of Life.

Core Features & Use Cases

  • Phased Migration Strategy: Guides you through a two-phase approach (W3C propagation first, then service-by-service OTel migration) to maintain trace integrity.
  • Language-Specific Guidance: Offers code snippets and configuration details for Go, Python, Node.js, Java, and Ruby.
  • Migration Checklists: Provides detailed checklists for both the migration process and safety considerations to prevent common pitfalls.
  • Use Case: You have a microservices architecture using Honeycomb Beelines and need to upgrade to OpenTelemetry before Beelines are fully unsupported. This skill will walk you through the entire process.

Quick Start

Use the beeline-migration skill to get a step-by-step guide for migrating your Go services from Honeycomb Beelines to OpenTelemetry.

Frequently Asked Questions about beeline-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from Honeycomb Beeline to OpenTelemetry?▼

This migration uses a two-phase strategy to maintain trace integrity: first implement W3C trace propagation across your services, then incrementally replace Beeline instrumentation with OpenTelemetry SDKs service-by-service.

What is the best way to maintain trace context when switching from Beeline to OpenTelemetry?▼

To maintain trace context, first standardize W3C trace propagation headers across your microservices before replacing any Beeline instrumentation with OpenTelemetry SDKs.

Can I migrate my Go microservices from Beeline to OpenTelemetry incrementally?▼

Yes, you can migrate incrementally by replacing Beeline instrumentation service-by-service. The guide provides specific code snippets and configuration details for Go, Python, Node.js, Java, and Ruby.

Do I need to check W3C trace propagation before migrating Beeline instrumentation?▼

Yes, verifying W3C trace propagation is the required first phase. Using the provided migration checklists ensures you handle safety considerations and prevent common tracing pitfalls before replacing SDKs.

Why should I migrate from Honeycomb Beeline to OpenTelemetry?▼

You should migrate because Honeycomb Beelines are reaching End of Life status. Migrating to OpenTelemetry SDKs ensures continued observability and long-term support for your microservices architecture.

Related Skills

Explore More Software Engineering Skills→
sandeepmvlsandeepmvl
21

distributed-tracing-rails

Configure OpenTelemetry distributed tracing for Rails microservices with W3C trace context propagation.

Community
Advanced
masermediagroup-stackmasermediagroup-stack
1

implementing-observability

Implement OpenTelemetry metrics, logs, and traces with LGTM stack deployment.

Community
Advanced
PostHogPostHog
58

omnibus-instrument-logs

Configure OpenTelemetry OTLP exporters to send structured logs to PostHog.

Official
Advanced
tense-itense-i
1

opentelemetry

Deploy OpenTelemetry Collector via Helm and configure telemetry pipelines in Kubernetes.

Community
Advanced