Free to read ยท Three levels
Prometheus: time series, PromQL, and alert contracts
Eighteen developed lessons cover Prometheus collection, series identity, PromQL, histograms, rules, relabeling, storage, routing, and validation.
Start learningIn this course
Follow a fictional warehouse service from instrument contracts through collection, series, queries, rules, and routing. The course emphasizes meaning: what a counter counts, which population an expression selects, and how identity, windows, absence, and limits change the decision.
Each level contains six complete lessons with explained examples, diagnostic mistakes, worked exercises, and official references. Python programs use local synthetic values only. Every PromQL, YAML, exposition, and flag block is non-executable teaching material; no Prometheus, Alertmanager, target, or receiver is started.
What you will learn
- Write metric, target, label, unit, and completion-boundary contracts.
- Interpret PromQL selectors, rates, aggregation, matching, histograms, and rules with their time semantics.
- Review relabeling, cardinality, storage, copies, routing, and tests while separating models from actual implementation evidence.
Your learning path
Three levels
Basic: collection and time-series meaning
Follow collection boundaries, series identity, metric types, targets, selectors, and counter rates.
- The pull model and measurement boundaries
- Time series, labels, and identity
- Counters, gauges, and exposition contracts
- Jobs, targets, and scrape health
- Selectors, vectors, and evaluation time
- Counter rates, increases, and resets
Intermediate: PromQL and rule contracts
Build compatible aggregation, matching, classic histograms, recording rules, alerts, and relabeling designs.
- Aggregation and meaningful error ratios
- Vector matching and metadata enrichment
- Classic histograms and quantile estimates
- Recording rules and derived series contracts
- Alert rules and state lifecycles
- Discovery and relabeling stages
Advanced: scale, persistence, and safe validation
Review cardinality, absence, local storage, remote copies, Alertmanager, and measurement-change evidence.
- Cardinality, churn, and ingestion limits
- Staleness, absence, and time comparisons
- Local storage, retention, and recovery assumptions
- Remote write, federation, and data copies
- Alertmanager routing, grouping, and suppression
- Rule testing and controlled measurement changes
Who this is for
- Developers, operations and platform engineers, and learners designing or reviewing Prometheus metrics, queries, and rules.
- Teams seeking interpretable measurements and reviewable alerts with controlled identity, cost, and evidence boundaries.
Before you start
- Basic services, HTTP, and programming knowledge; YAML and monitoring familiarity helps but system administration experience is unnecessary.
- Basic Python reading is sufficient for calculations, with no cloud account, running service, or package installation required.