It’s hard to live with them, but even harder without them. Events \u2013 indicators of a healthy environment or signs of disease.<\/p>\n
According to ITIL<\/a>, event can be defined as \u201cany change of state that has significance for the management of a configuration item (CI) or IT service.\u201d<\/p>\n Imagine this as a patient lying in a hospital bed and being connected to all those fancy (let\u2019s be serious \u2013 very useful) devices. Properly configured, they can give a lot of needed (sometimes life-saving) information so doctors always have a clear picture about the state of the patient. But, if they produced useless reports and created information overflow, information that was needed to save the patient\u2019s life could get lost. It\u2019s the same in an IT environment.<\/p>\n Service operation procedure<\/a>\u00a0is responsible for “keeping the lights on,” i.e. taking care of live services. To execute this responsibly and efficiently, service operations need to know the status of the infrastructure and services<\/a> in their responsibility, as well as be able to detect any deviation from normal or expected operation. Events are the instruments that are used. Events are usually recognized through notifications created by an IT service, CI (configuration item)<\/a> or monitoring tool. And, that\u2019s where the party begins. Someone has to define which monitoring data will be used, what they mean and what to do with them. That is the purpose of the Event Management process. Or, to put it officially, the purpose of event management is to manage events throughout their lifecycles.\u00a0Lifecycle<\/em>\u00a0means activities to detect events, make sense of them and determine appropriate action.Why events and event management?<\/h2>\n
\n