Monitoring a mixed estate
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design monitoring, alerting, and logging across owned, SaaS, and on-premises components.
Planned topics
- Four views: infrastructure health, application metrics, business metrics (orders per minute), and end-to-end synthetic checks.
- SaaS components: monitor from outside with synthetic checks and provider status feeds; do not assume the vendor will tell you in time.
- Correlation: a trace or order ID passed across systems makes support possible.
- Alert on symptoms that matter to the business, with severity and routing; avoid alert floods.
- Logs: central, searchable, with sensitive data excluded and retention set.
Draft outline details
Demonstration
a monitoring map: component, owner, signals, alert, destination; SaaS rows use synthetic checks and webhook failure rates.
Check your understanding
How do you monitor a SaaS you cannot install agents in?
Show answer
Synthetic checks, integration error rates, and the vendor's status feed.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.