Skip to main content

Event Management Reactive to Proactive

I have been asked by many students, how do you move from that role as the fire fighter resolving incidents to the role of being able to prevent them from occurring in the first place? Much of this has to do with good design and a strong proactive problem management process, but a solid event management process is an excellent offensive weapon in the prevention of impacting incidents in your environment.

Event Management is the process that gives IT the ability to detect events, make sense of them and determine the appropriate control action. It is the basis for our operational monitoring and control. This gives us a way to compare actual performance against what was designed and written in SLAs. What is perfect about event management is that we can apply it to any aspect of our environment from delivery of a service, monitoring an individual CI, environmental conditions to software license usage.

In conjunction with the other Service Management processes, along with both passive and active monitoring tools, Event Management can indicate a change in the status of a CI, allowing the early response of the appropriate person or team. This enhances our ability to act proactively in the prevention of exceptions or incidents and insure that we can deliver those desired business outcomes without interruption. Event Management provides the foundation for creating automated operations, increasing effectiveness and efficiencies by allowing more expensive human resources to do the more complex tasks of finding ways to create a competitive advantage for the business.

Event management does not begin the day we go live with a new or changed service. In the design stage of the SM lifecycle we identify the events we want to detect. We define these notifications. Is it regular operations? Is it something unusual, but not exceptional? Or could it be some type of exception. In Transition we build and test these notifications, the tools we will use to generate them and define roles and responsibilities. In operations we implement.
  • Event detection & filtering  
  • Determine significance: Informational, Warning or Exception 
  • Correlation: Determine response on a set of predefined rules
  • Triggers: Mechanism used to initiate a response
  • Response selection: event logged, auto response, alert and human intervention. Open an RFC, open an incident or open a problem
  • Review actions: handled correctly, track trends or counts
  • Close event

Through the implementation of these activities we can begin to proactively monitor availability, reliability, capacity and overall performance and move our organizations into a position of prevention vs reaction. 

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th