Observability · Difficulty 3 of 5 · 20 min
An error spike no alarm noticed
A function threw elevated errors yesterday, but its error alarm never fired and nobody heard about it. The alarm has changed state before. Two notification channels exist, neither wired up, each labelled with its purpose. Make the next spike reach the right people.
Where the symptom shows: Lambda
Take this challenge on a live account
A live AWS account, already broken, and a clock. You fix it with the provider's own console and command line, then read a report of how you worked. We host the cloud account. Nothing lands on your bill.
More challenges
- ObservabilityLog storage costs keep climbingAWS Config · 15 min · level 3
- ObservabilityTwo incidents that alerted nobodyLambda · 20 min · level 3
- ObservabilityEvery run fails and nothing explains whyStep Functions · 20 min · level 3
- ObservabilityNo trace of public API trafficAPI Gateway · 15 min · level 2
- ObservabilityAssistant activity is no longer recordedBedrock AgentCore · 10 min · level 1
- ObservabilityModel usage leaves no recordAmazon Bedrock · 10 min · level 1