If I monitor it, I want to Alert on it

Donald_Francis

Why is the list of items that we can monitor but not alert on growing (thinking across all modules)?

Why would I want to monitor something but never alert on it?  In my mind if I do one I automatically want both.

Some Examples:

-NTA

I would love to alert on things like X amount of traffic on X port, a single conversation going over X percentage of the link etc etc

-QOS

alert on X amount of drops in X class , X amount of traffic in X class

-VM

We have all these new VM specific stats with 10.1 but can we alert on them?

ESX box X over X amount of CPU, or X amount of RAM etc

cgregors

For the business, the information that is collected by Monitoring has a historical / trending value

Monitoring as a business process is also referred to as "Event Management" in ITIL.

In ITIL, Event Management feeds data into "Capacity Management".

 

So, even though you might not alert on a data point that you are collecting, the long term value of the data is still there when you start doing capacity planning.

Example: The response time of a web page changes very slowly. It may only increase 1-2 ms per week on average. Without a lot of data over a long period of time, you cannot do the capacity prediction of when to expand or upgrade the hardware behind the website.

So while you may not alert on the data point, perhaps you should report on the data point on a quarterly or yearly schedule