Self-Hosted Observability Directory

Migration plans

Migration Playbooks

Vendor-specific plans for replacing observability SaaS with self-hosted open-source stacks.

Discovery is only the first step. These playbooks turn the directory into practical migration plans: target stack options, rollout phases, acceptance checks, and risks to handle before cutting spend.

Datadog

8-12 weeks

A phased path for moving metrics, logs, traces, dashboards, and alerting away from Datadog without losing operational coverage.

Difficulty
High
Primary stack
SigNoz, Prometheus, Grafana, Grafana Loki

Honeycomb

8-12 weeks

A cautious path for replacing Honeycomb-style event analysis with OpenTelemetry pipelines, trace backends, and queryable logs.

Difficulty
High
Primary stack
OpenTelemetry Collector, Grafana Tempo, SigNoz, Uptrace

New Relic

6-10 weeks

A migration plan for teams replacing New Relic APM, logs, infrastructure metrics, and dashboards with OpenTelemetry-native tooling.

Difficulty
Medium-high
Primary stack
SigNoz, Uptrace, OpenTelemetry Collector, Prometheus

Sentry

4-8 weeks

A focused plan for replacing hosted Sentry with self-hosted error tracking while preserving release, source map, alerting, and ownership workflows.

Difficulty
Medium
Primary stack
Sentry (Self-Hosted), GlitchTip, Grafana OnCall, OpenTelemetry Collector

Splunk

10-14 weeks

A practical plan for moving expensive Splunk log search and operational dashboards to open-source log pipelines and search backends.

Difficulty
High
Primary stack
OpenObserve, Grafana Loki, Quickwit, Parseable