observabilitylisted
Install: claude install-skill xobotyi/cc-foundry
# Observability
**If you cannot ask arbitrary questions about your system's behavior from the outside, your system is not observable —
it is merely monitored.**
---
## The Three Pillars
<pillars>
### Logs — What Happened
Logs are timestamped, discrete event records. They capture **what happened** at a specific moment: an error thrown, a
user action, a configuration loaded, a connection refused.
**Use logs when you need:**
- Rich diagnostic context for a specific event
- Debugging information with full error details and stack traces
- Audit trails of who did what and when
- Record of discrete state transitions
**Logs are poor at:**
- Showing aggregate system health (use metrics)
- Tracing request flow across services (use traces)
- High-frequency numeric trends (too expensive at volume)
### Metrics — How Is It Doing
Metrics are numeric measurements aggregated over time. They capture **how the system is performing** as quantitative
time series: request rates, error percentages, latencies, queue depths, resource utilization.
**Use metrics when you need:**
- Real-time health signals and alerting
- Trend analysis over hours, days, weeks
- Capacity planning and saturation monitoring
- Pre-aggregated data that scales cheaply regardless of traffic
**Metrics are poor at:**
- Explaining _why_ something is broken (use logs)
- Showing the path of a single request (use traces)
- Storing per-event detail (cardinality explosion)
### Traces — How Did It Flow
Traces record t