Event Management Best Practices 1 488

Embed Size (px)

Citation preview

  • 8/8/2019 Event Management Best Practices 1 488

    1/21

    drive

    Event ManagementBest Practices

    BMC Software

  • 8/8/2019 Event Management Best Practices 1 488

    2/21

    2003 BMC SoftwareNovember 24, 20102

    O verview

    BSM and Event Management Incident Management and Problem Management Principles of Event Management Best Practices

    D ata AcquisitionNormalizationEnrichment Correlation and Root Cause AnalysisConsole Consolidation

    AutomationNotificationEscalationReporting

    BenefitsCustomer ExamplesBMC Software Solutions

  • 8/8/2019 Event Management Best Practices 1 488

    3/21

    2003 BMC SoftwareNovember 24, 20103

    Event Management is part ofBusiness Service Management

    Service Impact ManagementD eals with the relationships betweenServices and IT (dependency andimpact)

    Service model definitionService impact

    Service availability Automate and visualize events

    Requires sophisticated Event Management

    Event ManagementD eals with receiving and manipulatingthe IT events

    Collect and process eventsD efine and manipulate eventsPerform notifications

    Requires well-developed Infrastructureand Application Management

  • 8/8/2019 Event Management Best Practices 1 488

    4/21

    2003 BMC SoftwareNovember 24, 20104

    Incident Management andProblem Management

    Event Management is comprised of Incident management Problem management

    The primary objective of incident management is to restore

    service as soon as possible to minimize any negative effect onbusiness services.The objective of problem management is to takes a proactiveapproach in defining preventative measures so that servicedisruptions do not occur.

  • 8/8/2019 Event Management Best Practices 1 488

    5/21

    2003 BMC SoftwareNovember 24, 20105

    Best Practices Principles

    Consistent processEvent management tools that achieve

    D ata AcquisitionNormalization

    Enrichment Correlation and Root Cause AnalysisConsolidation

    AutomationNotificationEscalationReporting

  • 8/8/2019 Event Management Best Practices 1 488

    6/21

    2003 BMC SoftwareNovember 24, 20106

    D ata Acquisition

    D ata acquisition encompasses all the methods by whichevent management information is collected. Thesemethods can be

    Push

    PullPublish/Subscribe

  • 8/8/2019 Event Management Best Practices 1 488

    7/21

    2003 BMC SoftwareNovember 24, 20107

    N ormalization

    N ormalization is the process of homogenizing event datainto a common event format.

    Specific values are always located in a specific field and called

    a specific nameRegardless of the source of an event, a standard set of data isassociated with all eventsReporting is made consistent and efficient Event data has a common definition

  • 8/8/2019 Event Management Best Practices 1 488

    8/21

    2003 BMC SoftwareNovember 24, 20108

    Enrichment

    Enrichment is the process of adding value to the originalevent data for the purpose of streamlining incidentmanagement and facilitating service management.

    Provides details that supplement trouble tickets and repairactionsExtends event data for correlation, automation, notification,and reporting functions

    Associates service data or other data, such as blackout periods, to an event that can be used in incident or problemmanagement

  • 8/8/2019 Event Management Best Practices 1 488

    9/21

    2003 BMC SoftwareNovember 24, 20109

    Correlation and Root Cause Analysis

    Correlation and root cause analysis are processes thatdetermine the source of a problem, identify sympatheticevents, and relate associated events.

    Focuses repair action and speeds service restoration forincidentsStreamlines the event data presented to operators bysuppressing event clutterTargets problem management efforts

  • 8/8/2019 Event Management Best Practices 1 488

    10/21

    2003 BMC SoftwareNovember 24, 201010

    Console Consolidation

    Consolidation is the process of delivering all events fromacross the enterprise to a single pane of glass.

    Manage more with less

    Reduce complexityLeverage existing infrastructure management toolsGain a bird s eye viewFacilitate service management and problem management

  • 8/8/2019 Event Management Best Practices 1 488

    11/21

    2003 BMC SoftwareNovember 24, 201011

    Automation

    Automation is the process of removing or reducing theneed for human intervention in event management whilepromoting service resiliency.

    Allows problems to be fixed at machine speedSupports escalation of events when repair criteria areexceededStreamlines event management workload on staff Enforces policies and processes

  • 8/8/2019 Event Management Best Practices 1 488

    12/21

    2003 BMC SoftwareNovember 24, 201012

    N otification

    N otification is the process of presenting incidentinformation to the right person in the right form at theright time, and verifying their receipt of the information.

    Speeds information about an incident to the trouble ticket system or repair expert Contacts a repair expert in a suitable mannerFrees operators from another rote taskSupports multiple forms of communication

  • 8/8/2019 Event Management Best Practices 1 488

    13/21

    2003 BMC SoftwareNovember 24, 201013

    Escalation

    Escalation is the process of heightening the severity of orbroadening the awareness about an incident if not beingaddressed in an appropriate and timely manner.

    Prevents incidents from falling through the cracksEnsures attention to the most critical problemsElevates the status of an event if the problem persists

  • 8/8/2019 Event Management Best Practices 1 488

    14/21

    2003 BMC SoftwareNovember 24, 201014

    Reporting

    Reporting is the process of disseminating informationthat reflects the measurement of service levelagreements, historical usage, or the performance ofservice delivery components.

    Summarizes event management detailsMeasures problem resolution effectivenessProvides consistent service delivery data

  • 8/8/2019 Event Management Best Practices 1 488

    15/21

    2003 BMC SoftwareNovember 24, 201015

    Best Practices Benefits

    Identifies affected services and prioritizes repair actionsthrough enrichment and correlationPinpoints the exact problem condition through acquisition andcorrelation

    Presents repair details through enrichment, such asPhysical device location or specific application/databaseResponsible department/staff expert Repair action to be taken

    Reduces incident management workload through automated

    repair actionD elivers consistent service reporting through acquisition andnormalization

  • 8/8/2019 Event Management Best Practices 1 488

    16/21

    2003 BMC SoftwareNovember 24, 201016

    Best Practices Benefits

    Speeds notification to the right person at the right time in theright form through notification and escalationReduces mean time to repair through escalation, notificationand automation

    Reflects problem areas that can be addressed through problemmanagement through reporting

  • 8/8/2019 Event Management Best Practices 1 488

    17/21

    2003 BMC SoftwareNovember 24, 201017

    Customer Example #1

    Consolidation, Notification, Correlation, and Root Cause Analysisat a National Bank

  • 8/8/2019 Event Management Best Practices 1 488

    18/21

    2003 BMC SoftwareNovember 24, 201018

    Customer Example #2

    Normalization, Enrichment, and Automationat a Telco Vendor

  • 8/8/2019 Event Management Best Practices 1 488

    19/21

    2003 BMC SoftwareNovember 24, 201019

    Customer Example #3

    Enrichment and Notificationat a Large Hospital

  • 8/8/2019 Event Management Best Practices 1 488

    20/21

    2003 BMC SoftwareNovember 24, 201020

    BMC Software EventManagement Solutions

    ProductsBMC Event ManagerPATROL Enterprise ManagerPATROL KM for Event Management PATROL agent domain

    only AlarmPoint by Invoq Systems

    Services

    Architectural Assessment Professional Services

  • 8/8/2019 Event Management Best Practices 1 488

    21/21

    drive

    Thank you!

    Questions?