What you will learn
- Monitoring
- Data freshness
- Connection state
- Time synchronization
Monitoring
Operational monitoring should expose data freshness, connectivity, account state and task health. A process being alive does not prove that its inputs are current or its outputs are being accepted.
Data freshness
Alerts need an actionable condition, severity and owner. An alert that fires continuously without a defined response becomes background noise. Test delivery and escalation rather than assuming configuration equals receipt.
Connection state
Runbooks describe concrete steps for common failures using the actual system's state and permissions. Include what evidence to collect and when to stop. A generic instruction to restart everything can destroy useful context.
Time synchronization
Service objectives should distinguish availability from correctness. A system that responds quickly with stale data is not necessarily healthy. Choose measures that reflect the decisions the service supports.
Worked example
A dashboard updates its clock while its market feed has stopped. Process liveness looks normal, but source timestamps reveal that the decisions would use stale observations.
Try it yourself
Define separate liveness and freshness checks and state which dependent activity should be withheld when freshness fails.
Show the worked solution
Liveness checks the service response; freshness checks the age of required source observations under a documented policy. Withhold decisions that require current data while preserving monitoring and recovery access.
Apply this to your course project
Run an incident drill with reconciliation and a documented shutdown.
Keep the calculation inputs, assumptions and decisions with your work. Practical exercises are self-reviewed; the scored knowledge checks assess the questions shown, not an independent certification of practical competence.