Scope of Task

We need documentation that helps users migrate from Honeycomb to SigNoz, covering both SigNoz Cloud and Self-Hosted SigNoz.

⚠️ IMPORTANT UPDATE: Honeycomb has officially moved to fully support and encourage the use of OpenTelemetry (OTel) as its primary standard for instrumentation, deprecating its older "Beeline" SDKs and "Honeycomb Distributions" by August 12, 2025.

This simplifies the migration path significantly since both Honeycomb and SigNoz now use OpenTelemetry as the standard.

Updated Migration Strategy

Given Honeycomb's transition to OpenTelemetry-first approach, our documentation should focus on:

For users already using OpenTelemetry with Honeycomb:

• Direct migration path to SigNoz (simply change OTLP endpoint)
• Highlight that no SDK changes are needed since both platforms use OpenTelemetry

For users still using legacy Honeycomb SDKs (Beelines, Honeycomb Distributions):

• Redirect them to Honeycomb's official migration documentation to move to OpenTelemetry first
• Then guide them to switch the OTLP endpoint to SigNoz

Tasks

1. Migration Overview

   • Emphasize that Honeycomb is now OpenTelemetry-native (post-August 2025)
   • Explain the simplified migration path for OpenTelemetry users
   • For legacy SDK users, provide links to Honeycomb's migration guides:
     • Migrate from Beelines
     • Migrate from Honeycomb Distributions

2. OpenTelemetry Configuration Update

   • Show how to change OTLP endpoint from Honeycomb to SigNoz
   • Provide configuration examples for different languages/frameworks
   • Highlight that existing OpenTelemetry instrumentation works without changes

3. Dashboards & Queries

   • Link to SigNoz dashboard templates and explain how to request new ones
   • Describe SigNoz's dashboard features (panels, filters, query builder, sharing)
   • Show equivalent functionality mapping from Honeycomb to SigNoz

4. Data Migration

   • Since both platforms use OpenTelemetry, focus on endpoint configuration
   • Explain how traces, logs, and metrics flow seamlessly to SigNoz
   • Address any data retention or historical data considerations

5. Metrics & SLOs

   • Explain migration of derived or custom Honeycomb metrics/SLOs to SigNoz metrics
   • Enable the Prometheus Receiver in SigNoz (link to config guide)
   • Demonstrate the SigNoz Metrics Explorer

6. Alerts

   • Map Honeycomb Triggers/SLOs to SigNoz alert rules
   • Provide examples and YAML samples for Terraform Operator management

Where Should the Docs Go?

• Landing File Path: docs/migration/migrate-from-honeycomb-to-signoz.mdx
• Files for specific topics: docs/migrations/migrate-from-honeycomb/ (otlp-endpoint-change, dashboards, metrics, alerts, legacy-sdk-migration)
• Metadata ID: migrate-from-honeycomb
• Title: Migrate from Honeycomb to SigNoz
• Sidebar Name: Migrate from Honeycomb under Migrate to SigNoz

Key Messaging Points

• Simplified Migration: Since Honeycomb is OpenTelemetry-native, migration is primarily about changing the OTLP endpoint
• No SDK Changes Needed: For users already on OpenTelemetry, existing instrumentation works as-is
• Legacy SDK Users: Direct them to Honeycomb's official migration documentation first
• Unified Observability: Highlight SigNoz's unified approach to logs, metrics, and traces
• Cost Benefits: Emphasize predictable pricing advantages in SigNoz

Resources

• Migrate From ELK
• SigNoz vs Honeycomb comparison
• Honeycomb's Beeline Migration Guide
• Honeycomb's Distributions Migration Guide

Additional Notes

• Emphasize that this is the ideal time to migrate given Honeycomb's deprecation timeline (August 12, 2025)
• The migration is now much simpler since both platforms are OpenTelemetry-first
• Focus on configuration changes rather than instrumentation changes
• Highlight SigNoz advantages: unified observability, predictable pricing, open-source flexibility