Dependency Map
Purpose
Map of platform dependencies — what the platform relies on, and what relies on it.
Upstream (platform depends on)
| Dependency | Used for | Failure impact |
|---|---|---|
| Grafana Cloud | Data plane (Mimir/Loki/Tempo) | Total ingest/query loss |
| Azure / AKS | Compute for collectors | Collection gaps |
glc_ access policies | Write auth | 401s, dropped data |
Downstream (depends on platform)
| Consumer | Depends on | Failure impact |
|---|---|---|
| Service teams | Dashboards, alerts | Blind to their own health |
| Grafana IRM | Alert events | No incident routing |
| On-call rotation | Paging signals | Missed escalations |
Diagram
[stub: dependency-map-diagram]— fill this in. Greppable doc-debt marker.
Local graph
Linked from 2 notes
Related notes
Signal Forge ADR-005: Separate collector configmaps per deployment mode
Keeps cloud and local Alloy collector configs in separate files rather than one conditional configmap, so each mode's exporters stay explicit and uncoupled.
Signal Forge ADR-003: Span metrics generated before tail sampling
Places the spanmetrics connector ahead of tail_sampling so RED metrics reflect all traffic instead of only the ~25% of traces that survive sampling.
Signal Forge ADR-002: SpanLink for async RabbitMQ propagation (not parent-child)
Uses a SpanLink, not a parent-child span relationship, to connect RabbitMQ consumer spans back to the producer span across async, retry-prone delivery.
Architecture Overview
Signal Forge's topology, service communication, trace propagation, and per-signal pipeline flow across local and Grafana Cloud deployment modes.