Maybe this is where Iv messed up. I perhaps did not RTFM correctly :). So far I have created 6 data points.
        1. OS drive             OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.0.0.0
        2. Hot spare            OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.4.0.0
        3. Raid Array Drive 1   OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.5.0.0
        4. Raid Array Drive 2   OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.5.0.1
        5. Raid Array Drive 3   OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.6.0.0
        6. Raid Array Drive 4   OID:1.3.6.1.4.1.1597.1.4.1.1.8.0.0.6.0.1

        Each OID can return a number 1 - 14 depending on the status.
And then I created 14 Thresholds:

1       Invalid                 Warning 
2       Optimal                 Info
3       Verifying               Info
4       Failed                  Critical
5       Warning                 Warning
6       Formatting              Info
7       FormatCertifying        Info
8       Missing                 Critical
9       Not Created             Warning
10      Degraded                Critical
11      Building                Info
12      Verify Fixing           Info
13      Abort Activity          Info
14      Reserved                Info

On the first (Invalid) threshold I set my min and max to 1. I done the same on each one for example 2 (Optimal) I set the min and max to 2. Do you think this is why I am having such a hard time. Did I just not set it up correctly?

There are a couple of things to say about this. The first one is that there is a difference between "data sources" and "data points". Data points are contained within data sources. I was curious if the SNMP data sources you created contained data points. This is the important part to get right first, before you go into creating thresholds.

Even without thresholds being defined you should see the data points being collected and written to disk when you run zenperfsnmp with the verbosity turned up.

The second thing is that using thresholds in this manner almost definitely not the best way to monitor this type of value(s). The reason for this is that a threshold creates an event when it is violated, not when it is met. For example, with your Invalid (1) threshold having the min and max set to 1. This threshold is going to fire a warning event anytime the returned value is NOT 1. As you can then imagine, if the result comes back as Optimal (2) all of the thresholds except for the Optimal one will create an event.

This kind of complex monitoring can really only be done correctly by creating an external script to do the logic for you and calling it through a COMMAND type data source.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to