Lesson 1 of 4 · Free to read
Session lesson
Performance, SLOs & Data-store Signals
Self-paced phase · ~8–12 focused hours across Lab A/B/C
Audience: Final-year students & early-career engineers
Prerequisites: obs-06-profiling-and-ebpf
Why this matters (5 minutes)
One availability SLO on “the api service” can be green while users wait forever for async fulfillment. MNCs define SLIs per user journey and write error-budget policies before the incident.
Learning outcomes
- Drive realistic load with k6
- Define latency + freshness SLIs for the order journeys
- Write recording rules and a one-page error-budget policy
- Add basic Postgres/Redis observability signals
Shared lab constants
| System | api (Express) → SNS → SQS → worker → S3 (+ Postgres/Redis from phase 07) |
| Stack | Grafana · Prometheus/Mimir · Loki · Tempo · Pyroscope · OTel Collector · Alloy |
| Rule | Extend the same repo every phase — never start a new toy app. |
What MNCs do in 2026
k6 (or similar) for load, journey-based SLIs/SLOs, multi-window burn-rate alerts, and first-class Postgres/Redis telemetry are standard SRE practice.
Teachable chunks (compressed from days 61–70)
Journeys not services
Sync /orders acceptance vs async “order in S3” freshness are different promises.
SLI shapes
Availability, latency, freshness, throughput — all good/valid ratios.
Policy beats vibes
25%/50%/100% budget actions agreed in advance (freeze features, page next tier, etc.).
Data stores
Connection pools, slow queries, Redis hit ratio — silent killers of freshness SLOs.
Mental model
Watch & learn
Course video
Course video
Worked example
Define “95% of /orders under 300ms / 30d” and “95% fulfilled within 10s / 30d”. Instrument order_fulfillment_duration_seconds on the worker. Add recording rules and error-budget-policy.md.
Hands-on path
Open Exercises next. Complete Lab A → B → C in order. Stretch is optional.
Phase checklist
- Two journey SLOs defined
- Recording rules work under k6
- Error-budget policy exists
Key takeaways
- Keep the same order pipeline — depth beats new toy apps
- Correlate signals before you SSH
- Write policies and catalogs your future on-call self can use
Credit
Curriculum themes inspired by the public Observability100 course (https://observability100.vercel.app/course/index.html); lessons and labs rewritten for AI-Tutor.
Observability phase lesson — Performance, SLOs & Data-store Signals.