Baggage header lab made our staging traces legible overnight. Still wrestling with cardinality on custom tags.
Omar · Test engineer · 5/5
Intermediate
Observability Signals for QA
Pair structured logs, traces, and metrics so testers can narrate incidents with evidence operations leaders respect.
Quality engineers increasingly own the story between failing tests and customer impact. You will craft log fields, align trace IDs with automated cases, and design lightweight dashboards that do not duplicate FinOps dashboards. Language stays clear of financial services trigger words per training policy.
Duration: 4 weeks · weekday evenings · Format: Virtual cohort · Level: Intermediate · Schedule: Weekday evenings · Certification track: Portfolio path
Indicative fee: SGD 1,760 — invoiced separately; see Money-Back Policy.
What is included
- Log field naming workshop aligned to OpenTelemetry conventions
- Trace-to-test-ID linking pattern using baggage headers
- Metric cardinality guardrails for QA-owned namespaces
- Runbook snippets that reference tests instead of screenshots only
- Sampling strategies when staging traffic is thin
- Role-play incident call with mentor feedback
- Ethical data minimisation checklist for SG deployments
Outcomes you rehearse
- Ship a three-panel dashboard stub narrating a mock incident
- Document a trace ID convention your sample repo adopts
- Deliver a runbook paragraph engineers called “actually usable” in review
Responsible instructor
Ravi Krishnan
Telemetry coach for regional SaaS; insists QA narrates evidence, not tool brands.
FAQ
We start from templates; deep PromQL mastery is not assumed.