Dashboard critique felt like an internal review—sharp but fair.
Advanced
Signals, Logs, and Traces in AWS
Observability is a writing problem as much as a tooling problem. You design metric namespaces, trace sampling policies, and structured logs that downstream teams can parse without regex heroics.
From ¥58,000 JPY
Included focus areas
- Metric namespace workshop with cardinality controls
- Trace sampling policy that survives budget review
- Structured JSON logging contract template
- Dashboard design critique with mentor scoring
- Incident timeline reconstruction drill
- Alarm fatigue reduction checklist
- Cross-account observability considerations
Artifacts you should exit with
- Publish a service dashboard your NOC can read
- Draft a sampling policy with trade-offs noted
- Pair a log field schema with trace ids
Mentor anchor
SRE-turned-instructor; focuses on readable incident artifacts.
Elliot Park
Primary reviewer for this track
Participant questions
We stay AWS-native; bring vendor docs if you want a 15-minute compare session during office hours.
Not in core labs.
No mobile client instrumentation.