This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Suppressing reboot alerts only on certain nodes?

rharland2012 over 10 years ago

I have a few printers that we manage for our EMEA colleagues. We poll these printers using SNMP.

These printers get turned on and off a good bit, and we invariably get quite a few reboot alerts as a result of this.

I decided to suppress the reboot notifications for these specific nodes.

To that end, I populated the 'Comments' field in their custom properties with the word 'Printer', and then modified the reboot alert definition in Advanced Alert Manager to only trigger the alert when Boot Time had changed (the default condition) and Comments field did NOT contain 'Printer'.

For some reason, however, that seems to have suppressed all reboot alerts for all nodes.

I'm not positive why this isn't doing what I think it should, or if I am simply misinterpreting the effective definition of the alert.

Any information or previous experience with this situation would be great to hear.

Thanks!

Top Replies

0 bluefunelemental over 10 years ago

Can you include a copy of your alert screen? It might be easier both to use the machinetype field for the printers in the suppression of the alert - do not trigger if machinetype starts with to Canon or something.
Cancel
Vote Up 0 Vote Down

Cancel
0 cahunt over 10 years ago

Machine type or Vendor is good(maybe best if you have same device types that you want reboot alerts on), or if you have a qualifying Custom Property to use. Also depending on your naming convention you may be able to trigger off that or a portion of it that denotes a printer.
To verify logic though could you post your alert argument?
Cancel
Vote Up 0 Vote Down

Cancel
0 rharland2012 over 10 years ago

I was doing it the other way - asking for the engine to check for two things before it triggered the alert.
Cancel
Vote Up 0 Vote Down

Cancel
0 netlogix over 10 years ago in reply to rharland2012

you might need to add a group that is "any" and add the Comments is not equal to printer and add another there that says Comments is empty - it's a weirdness of SQL that if the field is null (because you didn't put anything in it), then it does show up when you say does not contain.
Cancel
Vote Up +1 Vote Down

Cancel
0 rharland2012 over 10 years ago in reply to netlogix

Ah, I see. Thank you.
Cancel
Vote Up 0 Vote Down

Cancel
0 rharland2012 over 10 years ago in reply to rharland2012

The funny thing is the original placement of that argument was on the suppression tab! It killed the reboot alerts - for everything.
My custom property value was taken directly from drop-down input - that is to say, the prelisted populated values when building a condition based on a custom property. I didn't have to type anything.
Cancel
Vote Up 0 Vote Down

Cancel
0 netlogix over 10 years ago in reply to rharland2012

The suppression tab is for global suppression. suppress everything if it is true anywhere. If you suppress "Comment = Printer", then if you have any comments that say printer for any node, suppress for every node until there isn't a comment of printer. Try to stay away from the suppression tab, unless you can not do it in the alert tab.
Cancel
Vote Up +1 Vote Down

Cancel