How do you define service levels in a wide-scale, labor-free manner? How useful is a solution that you have to define different criteria for every device and every monitored element? If you are managing a large network, the amount of labor and on-going maintenance required is virtually infinite, making it difficult and labor intensive to get right.

So how does AutoNOC solve this problem?

AutoNOC acquires, organizes, and correlates information about the systems, networks, and applications within an organization. It assigns service levels to all of these based on generic adaptive expressions. The following picture shows an example service level definition for an AutoNOC probe:

If you are monitoring the amount of bandwidth available across a network and you want to receive an e-mail when any pipe reaches 60% how do you do this? How do you do this when every pipe is a different size? 60% of what? In legacy systems, you will have to write a rule for each and every network pipe!

AutoNOC's adaptive expressions are defined once and automatically adapt to a given instance. This makes it possible to define a rule once that says alert on 60% full, and have it work to with all interfaces and devices on the network!

The amount of labor this feature saves probably doesn't seem like much, until you sit down with a legacy management solution and try to do it for yourself. Only then will you realize how valuable adaptive service levels are!