statsdlisted
Install: claude install-skill xobotyi/cc-foundry
# StatsD
Choose the right metric type, name it with dot-delimited hierarchy, tag dimensions instead of encoding them in names.
StatsD is fire-and-forget: UDP means zero latency impact, but wrong metric types or bad naming corrupt your data
silently.
## References
- **Metric types** — [`${CLAUDE_SKILL_DIR}/references/metric-types.md`]: Wire format details, type comparison, sampling
correction
- **Naming** — [`${CLAUDE_SKILL_DIR}/references/naming.md`]: Graphite namespace mapping, character rules, naming
examples
- **DogStatsD** — [`${CLAUDE_SKILL_DIR}/references/dogstatsd.md`]: Events format, service checks, protocol versions,
distributions vs histograms
- **Aggregation** — [`${CLAUDE_SKILL_DIR}/references/aggregation.md`]: Flush mechanics, Graphite downsampling, DogStatsD
aggregation, timestamps
- **Client patterns** — [`${CLAUDE_SKILL_DIR}/references/client-patterns.md`]: High-throughput tuning, error handling,
K8s deployment, UDS configuration
- **Backends** — [`${CLAUDE_SKILL_DIR}/references/backends.md`]: statsd_exporter config, Telegraf setup, migration
guides
## Metric Types
Wire format: `<metric_name>:<value>|<type>[|@<sample_rate>][|#<tags>]`
### Decision Matrix
| Question | Type |
| ------------------------------------- | ---------------------------------- |
| How many times did X happen? | Counter (`c`) |
| What is X right now? | Gauge (`g`)