Alarms, Response,
and Automated Actions
Once a problem is detected, what happens? Who gets contacted, when, and under what
criteria? How do you define these rules in a large environment? What happens when an
employee who is receiving alerts quits?On the surface this seems quite simple. It's just alerts isn't it?
But the truth, as in all things that seem simple, is that the devil is in the details. The
majority of legacy management software requires you to implement the specifics of each and
every alert. Not so with AutoNOC!
AutoNOC features a robust alarm system
that is built-on top of dynamic sets. Sophisticated relationships
are made easy with this one-two punch (Alarm-Set) model. Because alarms are built on top
of sets, very sophisticated wide-scale alarms may be easily defined. For instance, you can
create a set that sends e-mail to different users at different times of the day, or
conversely, monitors different devices at different times during the day!
Consider when you are managing 1,000s of
devices, and some criteria changes? Or you need to add devices? With legacy systems, you
will have to make 100s of changes to insure your management system still works.
With AutoNOC alarms you only need change
the set. This philosophy carries itself forward throughout all related activities. The
result is that it requires far less labor to maintain in real network scenarios. |
