Signal Catalog
Purpose
Canonical catalog of the signals the platform supports and the golden signals every service should emit.
Golden signals (per service)
| Signal | Type | Example |
|---|---|---|
| Request rate | metric | http_server_requests_total |
| Error rate | metric | ratio of 5xx / total |
| Latency | metric | request duration histogram (p50/p95/p99) |
| Saturation | metric | CPU / memory / queue depth |
| Logs | log | structured, correlated by trace_id |
| Traces | trace | end-to-end spans, sampled per policy |
Signal inventory
[stub: signal-inventory-table]— fill this in. Greppable doc-debt marker.
Conventions
- All signals carry the standard resource attributes — see Naming & Label Schema.
- New signal types go through a cardinality review — see Cardinality Governance.
Related
Local graph
Linked from 4 notes
Metrics Instrumentation Guide
How to instrument a service for **metrics** on the ShipSolid observability platform.
Traces Instrumentation Guide
How to instrument a service for **distributed traces** on the ShipSolid observability platform (OTel
Quickstart: Onboard in 30 Minutes
Get a service emitting metrics, logs, and traces to Grafana Cloud in **30 minutes**.
01 — Platform Architecture
How the platform is built — views, planes, signals, and the decision record indexes.
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.