一键在 Manus 中运行任何 Skill

beeline-migration

星标17

分支7

更新时间2026年2月26日 14:09

Step-by-step guide for migrating from Honeycomb Beelines (End of Life) to OpenTelemetry instrumentation. Trigger phrases: "migrate from Beelines", "upgrade from Beeline to OpenTelemetry", "migrate to OTel", "replace Beelines", "Beeline end of life", "Beeline EOL", "switch from Beeline to OTel", "migrate Go Beeline", "migrate Python Beeline", "migrate Node Beeline", "migrate Java Beeline", "migrate Ruby Beeline", "W3C trace headers", "W3C propagation", "incremental migration to OpenTelemetry", or any request about migrating from Honeycomb Beelines to OpenTelemetry SDKs.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

honeycombio

honeycombio/agent-skill

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Beeline to OpenTelemetry Migration

Step-by-step guide for migrating from Honeycomb Beelines (now End of Life) to OpenTelemetry instrumentation.

Status

Honeycomb Beelines have reached End of Life and are archived. All new instrumentation should use OpenTelemetry. Existing Beeline users should migrate as soon as practical.

Migration Strategy

Migration follows a two-phase approach that allows incremental, service-by-service migration without breaking distributed traces.

Phase 1: Enable W3C Trace Propagation (All Services)

Before migrating any service to OTel, all services must support W3C trace headers. This enables Beeline and OTel services to share trace context.

Upgrade each Beeline to the minimum version supporting W3C headers
Configure each Beeline to use W3C propagation format
Deploy all services with W3C enabled
Verify: Traces still link correctly across services

Minimum Beeline versions for W3C support:

Language	Minimum Version
Go	1.4.0
Java	1.7.0
Node.js	3.2.2
Python	2.18.0
Ruby	2.8.0

Phase 2: Migrate Each Service to OTel (One at a Time)

After all services support W3C headers:

Choose a service to migrate (start with leaf services — fewest dependencies)
Replace Beeline SDK with OpenTelemetry SDK
Configure OTLP exporter to point to Honeycomb
Add auto-instrumentation libraries
Replicate any custom Beeline instrumentation in OTel
Deploy and verify traces still connect
Repeat for next service

Key rule: Complete Phase 1 across ALL services before starting Phase 2 on ANY service.

W3C Propagation Configuration

Go Beeline

beeline.Init(beeline.Config{
    HTTPPropagationHook: propagation.W3C,
})

Python Beeline

beeline.init(
    http_trace_propagation_hook=beeline.propagation.w3c.http_trace_propagation_hook,
    http_trace_parser_hook=beeline.propagation.w3c.http_trace_parser_hook,
)

Node.js Beeline

const beeline = require("honeycomb-beeline")({
    httpTraceParserHook: beeline.w3c.httpTraceParserHook,
    httpTracePropagationHook: beeline.w3c.httpTracePropagationHook,
});

For Java and Ruby configurations, consult ${CLAUDE_PLUGIN_ROOT}/skills/beeline-migration/references/w3c-propagation.md.

Service Migration Checklist

For each service being migrated from Beeline to OTel:

Migration Safety Checklist

Complete Phase 1 across all services before starting Phase 2 — mixed propagation formats break trace linking across service boundaries
Keep OTEL_SERVICE_NAME identical to the Beeline service name — Honeycomb uses this as the dataset name, and changing it splits your data into a new dataset
Audit all Beeline addField() calls before removing the Beeline SDK — each one needs a corresponding span.set_attribute() in OTel to preserve your query dimensions
Compare OTel auto-instrumentation field names against Beeline field names — OTel may use different attribute names (e.g., http.request.method vs request.method), and dashboards or SLIs referencing the old names will need updating

Additional Resources

Reference Files

${CLAUDE_PLUGIN_ROOT}/skills/beeline-migration/references/migration-steps-by-language.md — Detailed migration code for each language
${CLAUDE_PLUGIN_ROOT}/skills/beeline-migration/references/w3c-propagation.md — Complete W3C configuration for all Beeline languages

Cross-References

For OTel SDK setup after migration, see the otel-instrumentation skill

同仓库更多 Skills

同仓库

otel-instrumentation

honeycombio/agent-skill

Provides guidance on OpenTelemetry SDK setup, custom instrumentation, and sending data to Honeycomb. Trigger phrases: "instrument my app", "add tracing", "set up OpenTelemetry", "configure OTel", "add custom spans", "add attributes to spans", "send traces to Honeycomb", "set up OTLP", "configure sampling", "add span events", "add span links", "set up tracing for [any language]", "configure the OTel Collector", or any request about OpenTelemetry SDK setup, custom instrumentation, or sending data to Honeycomb.

2026-07-1717

create-honeycomb-board

honeycombio/agent-skill

Design and then create a board (dashboard) in Honeycomb with queries and SLOs. Trigger phrases: "create a board", "make a board", "build a dashboard", "create a Honeycomb board", "make a dashboard in Honeycomb", "set up a board", "dashboard for my service", "visualize service health", "golden signals dashboard", "set up monitoring board", or any request to design and create or build a Honeycomb board or dashboard.

2026-07-1517

otel-genai-instrumentation

honeycombio/agent-skill

Guides instrumentation of GenAI/LLM applications with OpenTelemetry for Honeycomb, including content capture and agent failure detection. Trigger phrases: "instrument my GenAI app", "add tracing to LLM calls", "trace AI agent", "instrument OpenAI", "instrument Anthropic", "GenAI observability", "trace tool calling", "LLM token usage", "instrument embeddings", "trace MCP", "GenAI metrics", "instrument LangChain", "add GenAI spans", "capture prompts", "capture LLM responses", "enable GenAI content capture", "streaming tracing", "trace streaming responses", or any request about instrumenting GenAI/LLM applications.

2026-07-1517

production-investigation

honeycombio/agent-skill

Structured workflows for investigating production issues in Honeycomb — the sequence of tool calls (context priming, broad query, BubbleUp, trace analysis, verification) and how to chain results between steps to reach root causes. Trigger phrases: "investigate production issue", "debug latency spike", "find root cause", "use BubbleUp", "analyze traces", "debug an outage", "why is my API slow", "errors are increasing", "health check", "SLO burning", or any request to investigate or debug production problems.

2026-07-1517

query-patterns

honeycombio/agent-skill

Opinionated guidance for constructing and interpreting Honeycomb queries on trace and event datasets — operation selection (percentiles not AVG, HEATMAP for distributions), relational field patterns (root., parent., any., none.), calculated fields, query math, and result interpretation (P99/P50 ratios, heatmap bands, TOTAL/OTHER rows, raw JSON via query_result_json). Use this skill when the user wants to query spans, traces, or log/event data in Honeycomb — requests like "show me latency", "error rate", "find slow requests", "find outliers", "interpret results", "relational fields", "calculated fields", or "download raw results". This skill covers all dataset types except metrics datasets (dataset_type=metrics) — for those, use metrics-queries instead.

2026-07-1517

slos-and-triggers

honeycombio/agent-skill

Decision heuristics for interpreting Honeycomb SLO compliance, budget burn rates, and trigger status — what the numbers mean and what action to take, including detecting misconfigured SLIs, deciding when to freeze deploys vs page on-call, and designing burn alert thresholds. Load this skill before calling get_slos or get_triggers. Trigger phrases: "check our SLOs", "are we meeting our SLOs", "which SLOs are healthy", "is the error budget OK", "are any alerts firing", "what's the burn rate", "set up an SLO", "create a trigger", "configure alerts", "set up burn alerts", "check trigger status", "starting on-call", "reliability picture", "should we freeze deploys", "is this SLO misconfigured", "are we within budget", "SLO is broken", "budget is negative", or any request about service level objectives, error budgets, burn rates, or alerting in Honeycomb.

2026-06-0517

name	beeline-migration
description	Step-by-step guide for migrating from Honeycomb Beelines (End of Life) to OpenTelemetry instrumentation. Trigger phrases: "migrate from Beelines", "upgrade from Beeline to OpenTelemetry", "migrate to OTel", "replace Beelines", "Beeline end of life", "Beeline EOL", "switch from Beeline to OTel", "migrate Go Beeline", "migrate Python Beeline", "migrate Node Beeline", "migrate Java Beeline", "migrate Ruby Beeline", "W3C trace headers", "W3C propagation", "incremental migration to OpenTelemetry", or any request about migrating from Honeycomb Beelines to OpenTelemetry SDKs.
metadata	{"version":"1.0.0"}