Study guide

8.1 Monitoring and Event Management Practice

ITIL 4 Specialist: Create, Deliver and Support Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Structure & Service Value Stream Fundamentals

1.1 CDS Exam Structure, Format & Certification Strategy 1.2 The Service Value System & Value Stream Architecture 1.3 Value Stream Mapping & Flow Metrics

2 Chapter 2: Organizational Structures & Team Culture

2.1 Organizational Structures & Team Models 2.2 Collaborative Culture & Positive Communication 2.3 Workforce Planning & Competency Models

3 Chapter 3: Integrated Information & Modern Technology

3.1 Information Models & Integrated Toolsets 3.2 Analytics, Collaboration & Work Visibility 3.3 Automation, RPA, AI/ML & CI/CD Pipelines

4 Chapter 4: Value Stream for Designing & Transitioning New Services

4.1 Anatomy of the New-Service Value Stream 4.2 Designing & Architecting Value Streams 4.3 Transition, Validation & Testing in Value Streams

5 Chapter 5: Practices for New-Service Creation

5.1 Service Design & Software Development Management 5.2 Deployment Management & Release Management 5.3 Service Validation, Testing & Change Enablement

6 Chapter 6: Value Stream for User Support

6.1 Anatomy of the User-Support Value Stream 6.2 Shift-Left Strategy in User Support 6.3 Multi-Tier Support vs. Swarming

7 Chapter 7: Practices for User Support & Restoration

7.1 Service Desk & Incident Management 7.2 Problem Management & Known Error Database 7.3 Knowledge Management & Service Level Management

8 Chapter 8: Monitoring, Event Management & Continual Improvement

8.1 Monitoring and Event Management Practice 8.2 Continual Improvement Models & Waste Elimination 8.3 Metrics, Reporting & Value Stream Telemetry

9 Chapter 9: Managing & Structuring Work

9.1 Managing Work as Tickets 9.2 Prioritizing Work & Managing Queues 9.3 Managing Backlogs & Work Bottlenecks

10 Chapter 10: Sourcing, Buy-vs-Build & Service Integration (SIAM)

10.1 Sourcing Models & Commercial Considerations 10.2 Buy vs. Build Decision Framework 10.3 Service Integration and Management (SIAM)

8.1 Monitoring and Event Management Practice

Key Takeaways Explain This Topic AI

The Monitoring and Event Management practice systematically observes services and components, recording and reporting selected changes of state identified as events.

Events are classified into three distinct categories: Informational (normal operations, audit trails), Warning (threshold reached, action recommended to prevent failure), and Exception (service breach or failure requiring immediate incident creation).

Modern observability expands traditional monitoring across three pillars: Logs (discrete immutable records), Metrics (aggregated numeric telemetry over time), and Traces (end-to-end distributed request journeys).

Alert correlation engines, topological event deduplication, and dynamic threshold tuning are critical mechanisms to eliminate alert fatigue and enable automated self-healing remediation.

Last updated: September 2026

8.1 Monitoring and Event Management Practice

Quick Summary: The Monitoring and Event Management practice systematically observes services and service components, recording and evaluating state changes to maintain operational health. In ITIL 4 CDS, this practice shifts from reactive alerts to holistic observability—integrating logs, metrics, and traces—while deploying intelligent correlation and automated remediation to eliminate alert fatigue and safeguard value stream velocity.

In the ITIL 4 Service Value System (SVS), the purpose of the Monitoring and Event Management practice is to systematically observe services and service components, and record and report selected changes of state identified as events. An event is defined as any change of state that has significance for the management of a service or other configuration item (CI).

While traditional IT operations treated monitoring as an isolated infrastructure tool, Create, Deliver and Support (CDS) positions it as an essential capability across both new-service and user-support value streams. It provides real-time telemetry across the four dimensions of service management, validating that services deliver agreed utility and warranty while supplying operational intelligence to Incident Management, Problem Management, Capacity and Performance Management, and Continual Improvement.

The Three ITIL Event Classifications

Treating every change of state as an emergency quickly overwhelms operational teams. ITIL 4 categorizes events into three classifications:

Event Classification Operational Definition System Significance & Examples Required Action

Informational A normal, expected operational change of state. Confirms routine tasks executed successfully (e.g., successful user login, scheduled batch job completed, microservice health check responding HTTP 200). Recorded in audit logs and system journals; no immediate operational intervention required. Evaluated during trend and capacity analysis.

Warning An operational condition where a threshold is approached or abnormal behavior is detected. Indicates that a service or CI is operating outside optimal parameters but has not yet failed (e.g., storage capacity reaches 85%, memory utilization hits 88%, transaction retry rate elevates). Evaluated by automated runbooks or specialists. Proactive intervention is recommended to prevent impending degradation or service breach.

Exception An operational breach, threshold violation, or outright component failure. Signifies that a service or CI has breached agreed performance baselines or failed completely (e.g., server panic, network link down, deadlocked database transaction, failed payment gateway). Requires immediate operational response. Typically triggers an automated Priority 1 or Priority 2 incident, fails over to a secondary node, or alerts on-call swarming teams.

Active vs. Passive Monitoring

Service telemetry relies on two complementary operational paradigms:

Active Monitoring (Synthetic & Polling): The monitoring tool actively generates synthetic transactions or interrogates target CIs at predetermined intervals (e.g., sending automated HTTP GET probes, executing synthetic headless-browser checkout journeys, pinging network gateways). Active monitoring is vital for validating availability and latency from the user perspective before customers encounter issues, particularly during off-peak hours when real user traffic is minimal.

Passive Monitoring (Event-Driven & Traps): The component itself emits operational telemetry when a state change occurs without being queried (e.g., SNMP traps, syslog error streams, operating system audit events, container crash payloads). Passive monitoring introduces minimal network overhead and provides granular internal diagnostic context during high-load operational periods.

Modern Observability: The Three Pillars

Traditional monitoring answers the binary question: "Is the system working?" In modern, microservice-based, cloud-native architectures, failures are emergent, non-linear, and distributed. CDS embraces observability , which answers: "Why is the system behaving this way?" Observability infers the internal states of a complex system based on its external outputs, anchored by three foundational pillars:

Logs (Discrete History): Immutable, timestamped text records of discrete events (e.g., JSON application logs, authentication journals). Logs provide granular forensic context for root cause analysis during post-incident investigations but require high storage capacity.

Metrics (Aggregated Telemetry): Quantifiable numeric values measured over fixed time intervals (e.g., CPU percentage, memory consumption, request latency percentiles, error rates). Metrics are computationally lightweight, ideal for real-time dashboards and automated threshold triggers.

Traces (Distributed Journeys): End-to-end representations of a single request journey traversing distributed services, APIs, databases, and message brokers. Traces break down end-to-end latency into discrete "spans," instantly revealing latency bottlenecks across asynchronous microservice boundaries.

Alert Correlation, Deduplication, and Preventing Alert Fatigue

A chronic failure mode in enterprise support is alert fatigue —the cognitive exhaustion experienced by support teams inundated by hundreds of uncoordinated, noisy alerts. When a core database switch fails, hundreds of downstream application servers, API gateways, and web frontends simultaneously emit high-priority alerts. If each alert generates an isolated ticket, teams are overwhelmed by the noise and miss critical signals.

Modern CDS architectures deploy intelligent alert correlation engines and AIOps capabilities to overcome this:

Event Filtering: Discarding benign, redundant, or irrelevant informational noise at ingestion.

Event Deduplication: Collapsing multiple identical alerts generated by a repeating anomaly within a specified time window into a single event record.

Topological Correlation: Using Configuration Management System (CMS) dependency maps to correlate symptom alerts from child CIs to the root cause CI (e.g., grouping 250 microservice timeout alerts under a single core database lock event).

Dynamic Threshold Tuning: Replacing brittle static thresholds (e.g., static 80% CPU alerts) with adaptive baselines that account for seasonal, daily, and diurnal traffic patterns.

Automated Event Response & Value Stream Health

The ultimate objective of Monitoring and Event Management in CDS is transforming reactive firefighting into proactive value stream protection. Through automated runbooks and self-healing systems, pre-authorized remediation scripts automatically resolve recurring warning and exception states (e.g., automatically spinning up additional Kubernetes pods, purging temporary log directories, cycling deadlocked connection pools).

These automated interventions are recorded as standard changes, feeding closed-loop data into Problem Management for defect elimination and Capacity and Performance Management for architectural right-sizing.

Common Exam Traps & Pitfalls

Common Exam Trap Why Candidates Stumble How to Neutralize It

Event vs. Incident Confusion Assuming every detected event requires an incident ticket. Remember an event is any change of state; only exceptions or unmitigated warnings causing business degradation warrant incidents.

Alert Volume as a Success Metric Believing that generating more alerts demonstrates superior monitoring. Recognize that excessive alerts cause alert fatigue; effective monitoring prioritizes actionable, correlated signal over raw volume.

Active vs. Passive False Equivalence Viewing active synthetic monitoring as a total replacement for passive traps. Treat active and passive monitoring as complementary: active verifies baseline user journeys; passive captures internal system telemetry.