Identifying Service Impact from a Flood of Data

Millions of events. Data points by the tens of millions. The large networks managed by service providers generate a vast volume of management data. To keep customers renewing, you need to use that data to quickly spot whether any of the services they're paying for are affected by infrastructure problems.

The challenge is discovering a problem that exists before the customers do. They have the advantage of using the application itself and will immediately notice issues. If you're lucky, they'll pick up the phone and talk to you. If you're not lucky, they're on the phone to someone else looking for an alternative.

The technology you need is infrastructure impact analysis. Infrastructure impact analysis performs three key functions:

1. Maintains a continuously-accurate model of the infrastructure supporting each of your customers' services
2. Provides real-time policy-based analysis of availability and performance within the context of each customer model
3. Identifies incidents and provides immediate root cause assessment

Perhaps you've had bad experiences attempting to extend traditional rules-based impact assessment used in the networking realm into a holistic service view. That's understandable. Rules take time to write, and are only useful if change is very slow. It's also very difficult to code rules that identify multiple potential failures from incomplete data.

By contrast, Zenoss is designed to deal with the high rates of change in a service provider network. Zenoss uses patent-pending "policy gate" impact assessment technology instead of static rules, and provides simple probabilities for the root cause of identified failures.

Related Resources

Datasheet

Zenoss Service Dynamics: Impact Management

Demo

Operational Visibility into your Cloud Architecture

Webinar

Introduction to Zenoss Service Dynamics