skip to content
promptdojo
_
[ save your spot ]
[ follow on x ]
Structured logs and alerts — step 2 of 7
ch 47 · monitoring, drift, cloud scale, and portfolio launch
2/7
promptdojo
_
›
phase 08 · ai/ml engineering
›
ch 47 · monitoring, drift, cloud scale, and portfolio launch
lesson 1 of 6 · structured logs and alerts
step 2 of 7 in this lesson
Your fraud-scoring service logs every request. Which alerting setup is the most useful?
1
Alert when a real symptom crosses a threshold — e.g. error rate > 5% or p95 latency > 1s — computed from the logs.
2
Alert on every single log line so nothing is missed.
3
Don't alert; check the dashboard manually once a week.
4
Only log free text, no fields — it's simpler.
check
Show hint
ch 47 · monitoring, drift, cloud scale, and portfolio launch
2/7
promptdojo
_
›
phase 08 · ai/ml engineering
›
ch 47 · monitoring, drift, cloud scale, and portfolio launch
lesson 1 of 6 · structured logs and alerts
step 2 of 7 in this lesson
Your fraud-scoring service logs every request. Which alerting setup is the most useful?
1
Alert when a real symptom crosses a threshold — e.g. error rate > 5% or p95 latency > 1s — computed from the logs.
2
Alert on every single log line so nothing is missed.
3
Don't alert; check the dashboard manually once a week.
4
Only log free text, no fields — it's simpler.
check
Show hint
park a thought