5 Replies Latest reply: Nov 8, 2012 8:02 AM by herwig RSS

Tabular Poller Alerting - what is actually the best approach for open arrays?

herwig

Hi,

 

hardware monitoring with alert triggering is mandatory for every network,

I am playing around with the typical topics - fans, power supplies, temperature, ... so here you always come across tabular SNMP data.

 

GUI presentation works fine in the meantime,

unfortunately I'm not able to find a state of the art UnDP advanced alerting documentation (I am also surprised that most similar thk questions are not answered yet).

 

It seems the actual clean approach for tabular SNMP alerting is to use the ROW ID parameter,

but this is only useful, when you know how much rows you have in your queries - in most cases I don't because different hardware has different assets.

 

Here an example to clarify my subject...

What exactly happens when I have following device fan status:

FAN NumberStatus
11
23
31

 

Status Legend from ENVMON MIB:

        SYNTAX  INTEGER {

                        normal(1),

                        warning(2),

                        critical(3),

                        shutdown(4),

                        notPresent(5),

                        notFunctioning(6)

 

... in case I created following alert:

UnDP-table-alert-without-rows1.png

 

So the "Status" variable based on above presumtion has as content: "1, 3, 1" which is actually an array.

My trigger rules match for values > 1 but not 5--> because this is the case for empty power slots.

 

Questions:

1. Does this alert trigger or not?2. Is it matching against every single field in the array regardless of the array length?

3. and if yes does, it matches againt the worst value (which is 3 in my example) or maybe only the first or last value, which would obviously lead to a wrong result in the trigger clause...

 

Thanks for any hints, I think this topic also riddles others....

Herwig

  • Re: Tabular Poller Alerting - what is actually the best approach for open arrays?
    jcherpeski

    I too am needing to get some sort of alert when a power supply goes out.  Following what you did, I was able to get an alert on a test device, when I shut the power off on the secondary supply.  I don't know for sure if it will work on other devices, as they are in production.  It did show the device lost a power supply.  When I pulled the power supply out and it was no longer in the device, I got a reset alert.  So that part seems okay.  

     

    What I want to be able to do is have a report on the web view that actually shows any devices that I am monitoring power supplies on show if the are normal or not.  Something that will allow me at a glance to see if there are any problems, even if an alert has gone out.

  • Re: Tabular Poller Alerting - what is actually the best approach for open arrays?
    jcherpeski

    More like the summary report for PS status for all the monitored devices.  I haven't spent the time yet to see if I can write the report to then run it as a web object.  I just need a bit of down time at work.

    • Re: Tabular Poller Alerting - what is actually the best approach for open arrays?
      herwig

      Maybe you look for something like that? Check it out:

       

      SELECT

           n.[Caption] Node

         , l.[Label] FanModuleLabel

         , s.[Status] Status

         FROM [CustomPollerStatus] s

           JOIN [CustomPollerAssignment] a ON a.[CustomPollerAssignmentID] = s.[CustomPollerAssignmentID]

                AND (SELECT [CustomPollerID] FROM dbo.[CustomPollers] WHERE OID = '1.3.6.1.4.1.9.9.13.1.4.1.3') = a.[PollerID]

           JOIN [CustomPollerLabels] l ON l.[CustomPollerAssignmentID] = a.[CustomPollerAssignmentID] AND l.[RowID] = s.[RowID]

           JOIN [Nodes] n ON n.[NodeID] = a.[NodeID]