Event Management: Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
{|
<itpmch><title>Event Management | IT Process Wiki</title>
! align="right" width="80%"|
<meta name="keywords" content="itil event management, event management itil, event management process, itil v3 event management, event management itil" />
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/Event_Management diese Seite auf Deutsch]
<meta name="description" content="The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process  aims to filter and categorize Events in order to decide on appropriate actions if required." />
|}
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Event_Management" />
<meta property="og:title" content="Event Management | IT Process Wiki" />
<meta property="og:description" content="The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process  aims to filter and categorize Events in order to decide on appropriate actions if required." />
<meta property="og:site_name" content="IT Process Wiki - the ITIL&#174; Wiki">
<meta property="og:type" content="article" />
<meta property="article:publisher" content="https://www.facebook.com/itprocessmaps" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="900" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Event Management|163px
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/Event_Management diese Seite auf Deutsch]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Eventos esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>
 
'''<span id="Overview">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description">The objective of <i>ITIL Event Management</i> is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process  aims to filter and categorize Events in order to decide on appropriate actions if required.</span></p>
<p><b>Part of</b>: <a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" title="ITIL Service Operation">Service Operation</a></html>
 
'''Process Owner''': [[Event Management#IT Operations Manager|IT Operations Manager]]
 
<p>&nbsp;</p>
 
==Process Description==
 
The activities and process objectives of the Event Management process are mostly identical in ITIL V3 and V2 (Event Management was part of ICT Infrastructure Management).
 
[[Image:Event-management-itil.jpg|right|thumb|500px|alt=Event Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Event-management-itil.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf ITIL Event Management (.pdf)]]]
Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL V3.
 
In ITIL 2011 Event Management has been updated to reflect the concept of [[Event Management#ITIL Event 1st Level Correlation|1st Level Correlation]] and [[Event Management#Event Management 2nd Level Correlation|2nd Level Correlation]].
 
The process flows reflect the more detailed guidance in the ITIL 2011 books. The process overview of [[Media:Event-management-itil.jpg|ITIL Event Management]] shows the key information flows (see fig. 1).
 
[[ITIL 4]] refers to Event Management as a [[ITIL_4#Service_management_practices|service management practice]], and has renamed the practice to "Monitoring and event management".
<p style="clear:both;">&nbsp;</p>
 
==Sub-Processes==
 
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<meta itemprop="itemListOrder" content="Ascending" />
<p><span itemprop="name" content="Event Management sub-processes:">These are the <strong class="selflink">ITIL Event Management</strong> sub-processes and their process objectives:</span>
</p>
<p><b><span id="ITIL_Event_Management_Maintenance" itemprop="itemListElement">Maintenance of Event Monitoring Mechanisms and Rules</span></b>
</p>
<ul><li itemprop="description">Process Objective: To set up and maintain the mechanisms for generating meaningful <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> and effective rules for their filtering and <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">correlating</a>.
</li></ul>
<p><b><span id="ITIL_Event_1st_Level_Correlation" itemprop="itemListElement">Event Filtering and 1st Level Correlation</span></b>
</p>
<ul><li itemprop="description">Process Objective: To <a href="/index.php/Event_Management#Event_Filtering_and_Correlation_Rules" title="Event Management">filter out</a> Events which are merely informational and can be ignored, and to communicate any Warning and Exception <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a>.
</li></ul>
<p><b><span id="Event_Management_2nd_Level_Correlation" itemprop="itemListElement">2nd Level Correlation and Response Selection</span></b>
</p>
<ul><li itemprop="description">Process Objective: To interpret the meaning of an <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event</a> and select a suitable response if required.
</li></ul>
<p><b><span id="ITIL_Event_Management_Review" itemprop="itemListElement">Event Review and Closure</span></b>
</p>
<ul><li itemprop="description">Process Objective: To check if <a href="/index.php/Event_Management#Event_Record" title="Event Management">Events</a> have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify <a href="/index.php/Event_Management#Event_Trends_and_Patterns" title="Event Management">trends or patterns</a> which suggest corrective action must be taken.
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>


'''ITIL Version''': ITIL Version 3 (ITIL V3)
==Definitions==


'''Process Objective''': To filter and categorize Events and to decide on appropriate actions. Event Management is one of the main activities of Service Operations.
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<meta itemprop="itemListOrder" content="Ascending" />
<p><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in the ITIL Event Management process to represent process outputs and inputs:</span>
</p>
<p><b><span id="Event" itemprop="itemListElement">Event</span></b>
</p>
<ul><li itemprop="description">see <a href="/index.php/Event_Management#Event_Record" title="Event Management">Event Record</a>
</li></ul>
<p><b><span id="Event_Categorization_Scheme" itemprop="itemListElement">Event Categorization Scheme</span></b>
</p>
<ul><li itemprop="description">The Categorization Scheme for Events supports a consistent approach to dealing with specific types of Events. Ideally, this scheme should be harmonized with the schemes to categorize CIs, Incidents and Problems.
</li></ul>
<p><b><span id="Event_Filtering_and_Correlation_Rules" itemprop="itemListElement">Event Filtering and Correlation Rules</span></b>
</p>
<ul><li itemprop="description">Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. <a href="/index.php/Event_Management#ITIL_Event_1st_Level_Correlation" title="Event Management">Event Filtering and Correlation</a> Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered.
</li></ul>
<p><b><span id="Event_Record" itemprop="itemListElement">Event Record</span></b>
</p>
<ul><li itemprop="description">A record describing a change of state which has significance for the management of a Configuration Item or service. The term <i>Event</i> is also used to mean an alert or notification created by any IT service, Configuration Item or monitoring tool. Events often require IT operations personnel to take actions, and may lead to Incidents being logged.
</li></ul>
<p><b><span id="Event_Trends_and_Patterns" itemprop="itemListElement">Event Trends and Patterns</span></b>
</p>
<ul><li itemprop="description">Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed.
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>


'''Part of''': [[ITIL V3 Service Operation|Service Operation]]
==Roles | Responsibilities==


'''Process Owner''': [[Roles within ITIL V3#ITIL V3 roles and boards within Service Operation|IT Operations Manager]]
'''<span id="IT Operations Manager">IT Operations Manager - Process Owner</span>'''
*An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.


'''<span id="IT Operator">IT Operator</span>'''
*IT Operators are the staff who perform the day-to-day operational activities.
*Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.


==ITIL V3 vs. ITIL V2: Event Management==
<p>&nbsp;</p>


* Essentially, the activities and process objectives of the Event Management process are identical in ITIL V2 and V3 (Event Management is part of ICT Infrastructure Management in ITIL V2)
{| class="wikitable" style="background: white;"
* Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL V3 process structure
|-
|+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="5"| '''Responsibility Matrix: ITIL Event Management'''
|-
! style="background:#ffffee; width: 40%; text-align:center"| ITIL Role / Sub-Process
! style="background:#eeeeee" | [[Event Management#IT Operations Manager|IT Operations Manager]]
! style="background:#eeeeee" | [[Event Management#IT Operator|IT Operator]]
! style="background:#eeeeee" | (Event Monitoring System)
! style="background:#eeeeee" | Other roles involved [[Event Management#Team|<small>[3]</small>]]
|-
|style="text-align:left;" |[[#ITIL Event Management Maintenance|Maintenance of Event Monitoring Mechanisms and Rules]]
| A[[Event Management#Accountable|<small>[1]</small>]]R[[Event Management#Responsible|<small>[2]</small>]]
| R
| -
| R
|-
|style="text-align:left;" |[[#ITIL Event 1st Level Correlation|Event Filtering and 1st Level Correlation]]
| A
| -
| R
| -
|-
|style="text-align:left;" |[[#Event Management 2nd Level Correlation|2nd Level Correlation and Response Selection]]
| A
| R
| R
| -
|-
|style="text-align:left;" |[[#ITIL Event Management Review|Event Review and Closure]]
| AR
| -
| -
| -
|-
|}


'''Remarks'''


==Sub-Processes of Event Management (ITIL V3)==
<span id="Accountable">[1] ''A: Accountable'' according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Event Management process.</span>


[[Image:overview_event_management_itilv3_thumb.jpg|frame|left|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf  Overview of the Event Management Process, ITIL V3 (.pdf)]]]
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Event Management.</span>


;Maintenance of Event Monitoring Mechanisms and Rules
<span id="Team">[3] In cooperation, as appropriate: IT Operations Manager, Access Manager, Capacity Manager, Availability Manager, IT Service Continuity Manager, Information Security Manager, Applications Analyst and/ or technical Analyst. [[ITIL Roles| &#8594; Role descriptions...]]</span>
:Process Objective: To set up and maintain the mechanisms for generating meaningful Events and effective rules for their filtering  and correlating.


;Event Filtering and Categorization
==Notes==
:Process Objective: To filter out Events which can be ignored, and to assign categories to Events indicating their significance.


;Event Correlation and Response Selection
<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p>
:Process Objective: To interpret the meaning of an Event and select a suitable response.


;Event Review and Closure
<p>&nbsp;</p>
Process Objective: To check if Events have been handled appropriately  and may be closed. This process also makes sure  that Event logs are analysed in order to identify trends  or patterns which suggest corrective action must be  taken.


<p><small>
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Process_Description">
<span itemprop="name">Process Description</span></a>
<meta itemprop="position" content="1"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Sub-Processes">
<span itemprop="name">Sub-Processes</span></a>
<meta itemprop="position" content="2"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Definitions">
<span itemprop="name">Definitions</span></a>
<meta itemprop="position" content="3"></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Roles_.7C_Responsibilities">
<span itemprop="name">Roles</span></a>
<meta itemprop="position" content="4"></span>
</span>
</small></p>


==Roles within Event Management (ITIL V3)==
<!-- define schema.org/WebPage --> <span itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description">
  <meta itemprop="alternativeHeadline" content="ITIL Event Management" />
  <meta itemprop="alternativeHeadline" content="Monitoring and Event Management" />
  <meta itemprop="name" content="Event Management" />
  <link itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Event_Management" />
  <meta itemprop="inLanguage" content="en" />
  <link itemprop="citation" href="https://wiki.de.it-processmaps.com/index.php/Event_Management" />
  <link itemprop="citation" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Eventos" />
  <meta itemprop="Headline" content="Event Management" />
  <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" />
  <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" />
  <span id="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="caption" content="ITIL Event Management">
  <meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="900" />
  <meta itemprop="representativeOfPage" content="true"/>
  <meta itemprop="dateCreated" content="2011-10-02" />
  <meta itemprop="dateModified" content="2020-06-20" />
  <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
    <meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/1/13/Event-management-itil.jpg/800px-Event-management-itil.jpg" />
    <meta itemprop="width" content="800" />
    <meta itemprop="height" content="600" />
  </span>
  <meta itemprop="keywords" content="Event Management" />
  <meta itemprop="keywords" content="ITIL Event Management" />
  <meta itemprop="keywords" content="Event Monitoring" />
  </span>
  <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" />
  <meta itemprop="author" content="Stefan Kempter" />
  <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
</span><p></html>


* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Operation|IT Operations Manager]] (Process Owner)
<!-- This page is assigned to the following categories: -->
* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Operation|IT Operator]]
[[Category:ITIL 4]][[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL practice]][[Category:ITIL process]][[Category:Service Operation|Event Management]][[Category:Event Management|!]]
<!-- --- -->

Latest revision as of 12:56, 31 December 2023

DE - ES - Event Managementdiese Seite auf Deutschesta página en español
DE - ES - Event Management


Objective: The objective of ITIL Event Management is to make sure Configuration Items (CIs) and services are constantly monitored. The Event Management process aims to filter and categorize Events in order to decide on appropriate actions if required.

Part of: Service Operation

Process Owner: IT Operations Manager

 

Process Description

The activities and process objectives of the Event Management process are mostly identical in ITIL V3 and V2 (Event Management was part of ICT Infrastructure Management).

Event Management ITIL
ITIL Event Management (.pdf)

Interfaces between Event Management and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL V3.

In ITIL 2011 Event Management has been updated to reflect the concept of 1st Level Correlation and 2nd Level Correlation.

The process flows reflect the more detailed guidance in the ITIL 2011 books. The process overview of ITIL Event Management shows the key information flows (see fig. 1).

ITIL 4 refers to Event Management as a service management practice, and has renamed the practice to "Monitoring and event management".

 

Sub-Processes

These are the ITIL Event Management sub-processes and their process objectives:

Maintenance of Event Monitoring Mechanisms and Rules

  • Process Objective: To set up and maintain the mechanisms for generating meaningful Events and effective rules for their filtering and correlating.

Event Filtering and 1st Level Correlation

  • Process Objective: To filter out Events which are merely informational and can be ignored, and to communicate any Warning and Exception Events.

2nd Level Correlation and Response Selection

  • Process Objective: To interpret the meaning of an Event and select a suitable response if required.

Event Review and Closure

  • Process Objective: To check if Events have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify trends or patterns which suggest corrective action must be taken.

Definitions

The following ITIL terms and acronyms (information objects) are used in the ITIL Event Management process to represent process outputs and inputs:

Event

Event Categorization Scheme

  • The Categorization Scheme for Events supports a consistent approach to dealing with specific types of Events. Ideally, this scheme should be harmonized with the schemes to categorize CIs, Incidents and Problems.

Event Filtering and Correlation Rules

  • Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. Event Filtering and Correlation Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered.

Event Record

  • A record describing a change of state which has significance for the management of a Configuration Item or service. The term Event is also used to mean an alert or notification created by any IT service, Configuration Item or monitoring tool. Events often require IT operations personnel to take actions, and may lead to Incidents being logged.

Event Trends and Patterns

  • Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed.

Roles | Responsibilities

IT Operations Manager - Process Owner

  • An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.

IT Operator

  • IT Operators are the staff who perform the day-to-day operational activities.
  • Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.

 

Responsibility Matrix: ITIL Event Management
ITIL Role / Sub-Process IT Operations Manager IT Operator (Event Monitoring System) Other roles involved [3]
Maintenance of Event Monitoring Mechanisms and Rules A[1]R[2] R - R
Event Filtering and 1st Level Correlation A - R -
2nd Level Correlation and Response Selection A R R -
Event Review and Closure AR - - -

Remarks

[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Event Management process.

[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within Event Management.

[3] In cooperation, as appropriate: IT Operations Manager, Access Manager, Capacity Manager, Availability Manager, IT Service Continuity Manager, Information Security Manager, Applications Analyst and/ or technical Analyst. → Role descriptions...

Notes

By:  Stefan Kempter , IT Process Maps.

 

Process Description  › Sub-Processes  › Definitions  › Roles