Watch – continually monitor configuration item behaviourAlert – communicate status changes using different medias to different groupsDocument – save history of failures, performance values, repair actions, alerts sentAct – self-healing systems
Three levels of monitoring – can be used to assess maturity level of the IT service organization
A hardware failure should not trigger alerts for its dependent configuration itemsITIL precludes the creation of a service catalog where each service is linked to its underlining resources thus permitting to know the incident impact instantly
One size does not fit all – send different messages to different teams at different times.
Severity means the time to repair/act upon is different. Type of information collected determines the target team.Weekend alerts need a special treatment, maybe send via SMS, special escalation procedures (managers not on site)
Environment MonitoringConcepts & Good Practices<br />R.Radünz<br />firstname.lastname@example.org<br />1<br />
Good Practices</li></li></ul><li>3<br />What you should knowMonitoring is only one small part of a larger scenario that includes a Service Desk function, Incident, Problem, Change, Release Management and other processes. Used alone, it will not transform your datacenter in a state-of-the-art showcase.Nonetheless, it is indispensable.<br />3<br />