This documentation will guide you through migrating from Honeycomb to SigNoz, leveraging the fact that both platforms now use OpenTelemetry as their primary instrumentation standard. With Honeycomb's transition to OpenTelemetry-first approach and deprecation of legacy SDKs by August 12, 2025, the migration path has been significantly simplified. This guide will walk you through the migration process for both SigNoz Cloud and Self-Hosted deployments.
Why Migrate to SigNoz?
SigNoz offers several advantages over Honeycomb:
Unified Observability: Logs, metrics, and traces in one platform
Cost-Effective: Predictable pricing without per-event charges
Open Source: Full control over your observability stack
OpenTelemetry Native: Built from the ground up with OpenTelemetry
Self-Hosted Option: Keep your data on your infrastructure
Migration Strategy
The migration strategy depends on your current setup:
If you're already using OpenTelemetry with Honeycomb, migration is straightforward - simply change your OTLP endpoint to point to SigNoz. No SDK changes or re-instrumentation required. If you're already using OpenTelemetry with Honeycomb, migration is straightforward - simply change your OTLP endpoint to point to SigNoz. No SDK changes or re-instrumentation required.
For Legacy SDK Users (Two-Step Process)
If you're still using Honeycomb's legacy SDKs, follow this approach:
- First: Migrate from legacy Honeycomb SDKs to OpenTelemetry:
- First: Migrate from legacy Honeycomb SDKs to OpenTelemetry:
Migration Guides
Please refer to the following guides for step-by-step instructions on migrating each component from Honeycomb to SigNoz:
- Migrating Data - Configure traces, logs, and metrics flow with unified data correlation and additional metrics sources
- Migrating Dashboards - Recreate boards and queries with enhanced visualizations
- Migrating Alerts - Convert triggers to alert rules with notification channels
