

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Still calibrating
click for more info
Not enough gems
Cost: 6 gems
1: Observability
incomplete
2: Alerts
incomplete
3: Responsible Disclosure
incomplete
4: Incident Severity and Triage
incomplete
5: Damage Control
incomplete
6: Postmortems
incomplete
7: Incident Reporting
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Alerts tell you when a monitored condition needs attention. They can come from metrics, logs, or other events. For example, you might want a Slack bot to ping your on-call engineer(s) when:
When an alert fires, the on-call engineer needs to actually know what to do. They should have documentation or tools that help them:
Keep documentation short, or even better, build it directly into your systems. If someone has to read three pages at 3 AM, it won't get read.
Individual authentication events are useful during an investigation, but nobody should have to spot an active attack by tailing a log.
Emit structured security alerts when authentication activity crosses a threshold.
These local counters model an alerting signal. A production deployment would aggregate events across application instances and route alerts through its monitoring system.
With Bearly Secure still running, run and submit the CLI tests from the project root.