Watches services and their components in a systematic way, recording and reporting chosen changes of state that are classed as events (a change of state that matters for managing a service or CI). It identifies and ranks events relating to information security, business processes, services and infrastructure, and decides how to respond, including to conditions that might lead to faults or incidents. Activities are: deciding what to monitor and setting the monitoring approach; putting monitoring in place and keeping it working, using built-in features and dedicated tools; setting the thresholds and criteria that decide which changes of state count as events and of which type (informational, warning, exception); setting handling policies for each type; and putting in place the processes and automation that make those policies work. An event showing a live issue starts incident management, and repeated out-of-range events start problem management. The practice assesses and actively improves the health of the environment, triggers internal engagement, informs design and demonstrates that transition succeeded, supports development environments, and guides how events are handled internally during delivery.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.