Event Management: Difference between revisions

From IT Process Wiki
No edit summary
Line 8: Line 8:
<br style="clear:both;"/>
<br style="clear:both;"/>


<html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p></html>
<p>&nbsp;</p>
<p>&nbsp;</p>


The objective of ''ITIL Event Management'' is to make sure CIs and services are constantly monitored. ''Event Management'' aims to filter and categorize Events in order to decide on appropriate actions if required.
'''<span id="Overview">Objective:</span>''' <html><span itemprop="description">The objective of <i><span itemprop="alternativeHeadline">ITIL <span itemprop="name Headline">Event Management</span></span></i> is to make sure CIs and services are constantly monitored. ''Event Management'' aims to filter and categorize Events in order to decide on appropriate actions if required.</span></p>
 
<p><b>Part of</b>: <a itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation" title="ITIL Service Operation">Service Operation</a></html>
'''Part of''': [[ITIL V3 Service Operation|Service Operation]]


'''Process Owner''': [[Event Management#IT Operations Manager|IT Operations Manager]]
'''Process Owner''': [[Event Management#IT Operations Manager|IT Operations Manager]]
Line 18: Line 18:
<p>&nbsp;</p>
<p>&nbsp;</p>


== ITIL Event Management ==
==Process Description==


==== Event Management Process ====
Essentially, the activities and process objectives of the Event Management process are identical in ITIL V3 and V2 (Event Management was part of ICT Infrastructure Management).  
 
Essentially, the activities and process objectives of the Event Management process are identical in ITIL V3 and V2 (Event Management is part of ICT Infrastructure Management in ITIL V2).  


[[Image:Event-management-itil.jpg|right|thumb|375px|alt=Event Management ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf ITIL Event Management]]]
[[Image:Event-management-itil.jpg|right|thumb|375px|alt=Event Management ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf ITIL Event Management]]]
Interfaces between [[Event Management]] and the other ITIL processes were adjusted in order to reflect the new ITIL process structure in ITIL 2007.
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 (''see Fig. 1'') reflect the more detailed guidance in the ITIL 2011 books.
 
<span id="Sub-Processes">''These are the [[Event Management|ITIL Event Management]] sub-processes:''</span>


<p>&nbsp;</p>
<p>&nbsp;</p>


;<span id="ITIL Event Management Maintenance">Maintenance of Event Monitoring Mechanisms and Rules</span>
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]].  
:Process Objective: To set up and maintain the mechanisms for generating meaningful [[Event Management#Event Record|Events]] and effective rules for their filtering and [[Event Management#Event Filtering and Correlation Rules|correlating]].


;<span id="ITIL Event 1st Level Correlation">Event Filtering and 1st Level Correlation</span>
The process flows (''see Fig. 1'') reflect the more detailed guidance in the ITIL 2011 books. The process overview of [[Media:Event-management-itil.jpg|ITIL Event Management]] is showing the most important interfaces (see Figure 1).
:Process Objective: To [[Event Management#Event Filtering and Correlation Rules|filter out]] Events which are merely informational and can be ignored, and to communicate any Warning and Exception [[Event Management#Event Record|Events]].
 
;<span id="Event Management 2nd Level Correlation">2nd Level Correlation and Response Selection</span>
:Process Objective: To interpret the meaning of an [[Event Management#Event Record|Event]] and select a suitable response.
 
;<span id="ITIL Event Management Review">Event Review and Closure</span>
:Process Objective: To check if [[Event Management#Event Record|Events]] have been handled appropriately and may be closed. This process also makes sure that Event logs are analyzed in order to identify [[Event Management#Event Trends and Patterns|trends or patterns]] which suggest corrective action must be taken.


<p>&nbsp;</p>
<p>&nbsp;</p>


==== Downloads ====
==Sub-Processes==
 
Use the following links to open the process overview of Event Management showing the most important interfaces:
 
* [[Media:Event-management-itil.jpg|ITIL Event Management (.JPG)]]
* [https://wiki.en.it-processmaps.com/images/pdf/process_overview_event_management_itilv3.pdf ITIL Event Management (.PDF)]


<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>&#160;</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><br />
</p><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><br />
</p><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><br />
</p><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>
<p>&nbsp;</p>
<p>&nbsp;</p>


==== ITIL Terms ====
==Definitions==
 
;<span id="Event">Event</span>
:see [[Event Management#Event Record|Event Record]]
 
;<span id="Event Categorization Scheme">Event Categorization Scheme</span>
: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.
 
;<span id="Event Filtering and Correlation Rules">Event Filtering and Correlation Rules</span>
:Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. [[Event Management#Event Management Correlation|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.
 
;<span id="Event Record">Event Record</span>
: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.
 
;<span id="Event Trends and Patterns">Event Trends and Patterns</span>
:Any trends and patterns identified during analysis of significant Events, which suggest that improvements to the infrastructure are needed.


<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%20Glossary#ITIL%20Glossary%20A-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>&#160;</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><br />
</p><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><br />
</p><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><br />
</p><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><br />
</p><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>
<p>&nbsp;</p>
<p>&nbsp;</p>


==== ITIL Roles ====
==Roles | Responsibilities==


;<span id="IT Operations Manager">IT Operations Manager - Process Owner</span>
'''<span id="IT Operations Manager">IT Operations Manager - Process Owner</span>'''
:An IT Operations Manager will be needed to take overall responsibility for all of the [[IT Operations Control|IT Operations]] activities. He will ensure that all day-to-day operational activities are carried out in a timely and reliable way.
*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.
<br />


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


<p>&nbsp;</p>
<p>&nbsp;</p>


{| border="1" cellpadding="5" cellspacing="0" style="text-align:center;" valign="top"
{| border="1" cellpadding="5" cellspacing="0" style="margin-left: auto; margin-right: auto; text-align:center;" valign="top"
|-
|-
| valign="top" colspan="5" style="background:#ffffdd;" align="center"| '''Responsibility Matrix: ITIL Event Management'''
|style="vertical-align:top; text-align:center" colspan="5" style="background:#ffffdd;"| '''Responsibility Matrix: ITIL Event Management'''
|-
|-
! width="40%" align="center" style="background:#ffffee;" | ITIL Role / Sub-Process
! style="background:#ffffee; width: 40%; text-align:center"| ITIL Role / Sub-Process
! style="background:#ffffee;" | [[Event Management#IT Operations Manager|IT Operations Manager]]
! style="background:#ffffee;" | [[Event Management#IT Operations Manager|IT Operations Manager]]
! style="background:#ffffee;" | [[Event Management#IT Operator|IT Operator]]
! style="background:#ffffee;" | [[Event Management#IT Operator|IT Operator]]
Line 96: Line 118:
! style="background:#ffffee;" | Other roles involved [[Event Management#Team|<small>[3]</small>]]
! style="background:#ffffee;" | Other roles involved [[Event Management#Team|<small>[3]</small>]]
|-
|-
| align="left" |[[#ITIL Event Management Maintenance|Maintenance of Event Monitoring Mechanisms and Rules]]
|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>]]
| A[[Event Management#Accountable|<small>[1]</small>]]R[[Event Management#Responsible|<small>[2]</small>]]
| R
| R
|
| -
| R
| R
|-
|-
| align="left" |[[#ITIL Event 1st Level Correlation|Event Filtering and 1st Level Correlation]]
|style="text-align:left;" |[[#ITIL Event 1st Level Correlation|Event Filtering and 1st Level Correlation]]
| A
| A
|  
| -
| R
| R
|  
| -
|-
|-
| align="left" |[[#Event Management 2nd Level Correlation|2nd Level Correlation and Response Selection]]
|style="text-align:left;" |[[#Event Management 2nd Level Correlation|2nd Level Correlation and Response Selection]]
| A
| A
| R
| R
| R
| R
|  
| -
|-
|-
| align="left" |[[#ITIL Event Management Review|Event Review and Closure]]
|style="text-align:left;" |[[#ITIL Event Management Review|Event Review and Closure]]
| AR
| AR
|  
| -
|  
| -
|  
| -
|-
|-
|}
|}
Line 130: Line 152:
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Event Management.</span>
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within Event Management.</span>


<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. [[Roles within ITIL V3| &#8594; Role descriptions...]]</span>
<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>


<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
==[ Infobox ]==
<html><table class="wikitable">
<tr>
<td>Link to this page:</td>
<td><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Event_Management">https://wiki.en.it-processmaps.com/index.php/Event_Management</a></td>
</tr>
<tr>
<td>Languages:</td>
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external text" href="https://wiki.de.it-processmaps.com/index.php/Event_Management" title="Event Management">Deutsch</a></span> | <span><a itemprop="citation" class="external text" href="https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_Eventos" title="Gestión de Eventos">espa&#xf1;ol</a></span></td>
</tr>
<tr>
<td>Image:</td>
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/1/13/Event-management-itil.jpg" title="Incident Management">ITIL Incident Management (.JPG)</a></td>
</tr>
<tr>
<td>Author:</td>
<td><span itemprop="author">Stefan Kempter</span>, <span itemprop="creator copyrightHolder publisher">IT Process Maps</span> &nbsp;&nbsp; <a rel="author" href="https://plus.google.com/111925560448291102517"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a></td>
</tr>
</table>
<p><small>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Process_Description" itemprop="url"><span itemprop="title">Process Description</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Sub-Processes" itemprop="url"><span itemprop="title">Sub-Processes</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Definitions" itemprop="url"><span itemprop="title">Definitions</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Event_Management#Roles_.7C_Responsibilities" itemprop="url"><span itemprop="title">Roles</span></a>
</span>
</small></p>
</div><!-- end of schema.org/WebPage --><p></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Operation|Event Management]][[Category:Event Management|!]]
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Operation|Event Management]][[Category:Event Management|!]]
<!-- --- -->
<!-- --- -->

Revision as of 21:25, 18 December 2013

<seo metakeywords="itil event management, event management itil, event management process, itil v3 event management, event management itil" metadescription="Event Management: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Event Management." />

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 CIs and services are constantly monitored. ''Event Management'' 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

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

Event Management ITIL
ITIL Event Management

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 (see Fig. 1) reflect the more detailed guidance in the ITIL 2011 books. The process overview of ITIL Event Management is showing the most important interfaces (see Figure 1).

 

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...

 

 

[ Infobox ]

Link to this page:
Languages: English | Deutsch | español
Image: ITIL Incident Management (.JPG)
Author: , IT Process Maps   

 ›  ›  ›