Am looking for some KPIs for Event Management. We have a fully established monitoring team that's supposed to send alerts for any potential eventualities. We have a degree of automation too (Patrol, Candle etc) and these tools are capable of opening auto-Incidents and flash reports to support.

What should be the KPIs for such a function? Ofcourse, I want to base them on my SLAs/OLAs example Service A requires 99.5% availability and have 24/7 online hours except for a weekly service outage period. Can I put something like "Incidents avoided due to monitoring" as a KPI? Does anyone have more of them?_________________regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill

Thanks John for being the first one as always. I thought I'll wait for Diarmind before any comments. But the purpose of the KPI is same as any other KPI and that of continual service improvement. Similar to Change Management KPI of Failed change where the KPI itself doesn't mean that the change owner is fired or sent to showers.

Event KPIs look like a tricky one. I need a few to put a value on the alerting systems we bought recently and to know what value the additional people are creating.

I thought of a few like - Incidents avoided due to Events, Changes triggered due to events, Proactive management of Problems.

Anything else do we know?_________________regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill

Event Management is a term I don't fully understand. Events seem to have a hazy boundary with incidents. I will have to think as I write.

So I'll start with the obvious. Event Management is about efficiently, effectively and appropriately managing the fact that an even has occurred in terms of its implications for the service(s).

Monitoring is probably the principle pro-active element.

Analysis is what determines the impact, potential impact, risk and cause. This could lead to preventive/remedial action (if its remedial, I would have said the event was an incident, I think), communication concerning the implications, raising a problem or alerting pro-active problem management that there is something worth a look, and some other stuff.

What can you measure? Well:
1.incidents (or perhaps service impacts - because I might want to call the event an incident) avoided.
2. incidents (ditto parenthetical comment) resolved sooner than if the alert had been from a service user with trouble.
3. problems spotted sooner as above.
4. capacity management more successful - don't know how you measure this, but good event management should mean greater control of server and service performance which should mean more accurate timing of needs such as adding processing power to the infrastructure.

As I write this I begin to feel that event management cuts across various disciplines, especially incident management, operations management, service level management and capacity management. I wonder how it can be looked at across those contexts in a holistic way beyond its principles.

Told you I didn't know much about it. Still, hope this helps._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

I don't see a problem putting KPIs against a function. In fact I prefer them there. The function is more than the team; in fact sometimes there is not a team mapped against the function and this could be a case in point._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718