Add observability roadmap doc with Datadog-equivalent target architecture #83

New issue

Closed

opened 2026-06-04 05:28:46 +00:00 by ldraney · 0 comments

ldraney commented

2026-06-04 05:28:46 +00:00

Owner

Type

Feature

Lineage

Child of ldraney/landscaping-assistant #43 (Observability & DORA metrics stack).

Repo

ldraney/landscaping-assistant

User Story

As a platform operator
I want a documented observability roadmap that maps Datadog capabilities to open-source equivalents
So that future observability work has a clear target architecture and phased rollout plan

Context

The platform has a solid observability foundation (Prometheus, Loki, Grafana, Alertmanager, DORA exporter, Blackbox probes) but is missing distributed tracing, continuous profiling, database query analysis, frontend RUM, SLO tracking, infrastructure visualization, and runtime security. This doc captures the full gap analysis and a 6-phase rollout plan using the Grafana ecosystem (Tempo, Pyroscope, Faro, Headlamp, Pyrra, Falco).

File Targets

Files the agent should modify or create:

docs/observability-roadmap.md -- new doc with target architecture mermaid diagram, gap analysis table, and phased rollout

Acceptance Criteria

Doc exists at docs/observability-roadmap.md
Mermaid diagram renders showing full target architecture
Gap analysis table maps every Datadog capability to open-source equivalent with status
6-phase rollout plan with per-phase scope and technology choices

Test Expectations

No test changes -- docs only

Constraints

Must align with existing docs/observability.md (current state doc)
Technology choices must fit Grafana ecosystem (Tempo, not Jaeger; Pyroscope, not standalone pprof)
All components must deploy via Terraform Helm releases in pal-e-platform

Checklist

PR opened
No unrelated changes

project-pal-e-platform -- platform observability stack
ldraney/landscaping-assistant #43 -- parent observability issue

### Type Feature ### Lineage Child of `ldraney/landscaping-assistant #43` (Observability & DORA metrics stack). ### Repo `ldraney/landscaping-assistant` ### User Story As a platform operator I want a documented observability roadmap that maps Datadog capabilities to open-source equivalents So that future observability work has a clear target architecture and phased rollout plan ### Context The platform has a solid observability foundation (Prometheus, Loki, Grafana, Alertmanager, DORA exporter, Blackbox probes) but is missing distributed tracing, continuous profiling, database query analysis, frontend RUM, SLO tracking, infrastructure visualization, and runtime security. This doc captures the full gap analysis and a 6-phase rollout plan using the Grafana ecosystem (Tempo, Pyroscope, Faro, Headlamp, Pyrra, Falco). ### File Targets Files the agent should modify or create: - `docs/observability-roadmap.md` -- new doc with target architecture mermaid diagram, gap analysis table, and phased rollout ### Acceptance Criteria - [ ] Doc exists at `docs/observability-roadmap.md` - [ ] Mermaid diagram renders showing full target architecture - [ ] Gap analysis table maps every Datadog capability to open-source equivalent with status - [ ] 6-phase rollout plan with per-phase scope and technology choices ### Test Expectations - [ ] No test changes -- docs only ### Constraints - Must align with existing `docs/observability.md` (current state doc) - Technology choices must fit Grafana ecosystem (Tempo, not Jaeger; Pyroscope, not standalone pprof) - All components must deploy via Terraform Helm releases in pal-e-platform ### Checklist - [ ] PR opened - [ ] No unrelated changes ### Related - `project-pal-e-platform` -- platform observability stack - `ldraney/landscaping-assistant #43` -- parent observability issue