What problem does it solve?
Investigating production issues requires querying time-series metrics, but unbounded queries against VictoriaMetrics can flood context with thousands of series and slow down root cause analysis. This Skill enforces a context-efficient workflow—statistics first, then instant queries, then capped range queries—so you get compact, actionable metric data.
Core Features & Use Cases
- Cardinality Discovery: The get_statistics.py script reports active series counts, top metric names, and top jobs before any heavy querying.
- Targeted MetricsQL Queries: Run instant or range queries with PromQL and MetricsQL extensions (WITH templates, rollup functions, label manipulation) with output limits.
- Label Discovery: List available labels and values scoped by series selectors to build precise filters.
- Use Case: During an incident, check the error rate for a service by running statistics on the job, then querying the 5xx rate ratio, then drilling into the top 5 offending services with topk.
Quick Start
Ask the agent to check the current error rate for the api job in VictoriaMetrics, starting with metric statistics and then running a topk-limited MetricsQL query.