I want to be able to reset the Message count when a Message goes from Major to Critical as an example, I need to do this for some of out over night alerts, what is the bestway to do this?
In the NAS probe open the 'Setup" -> 'Message Suppression' tab. Under there you should see a check box for 'Reset Suppression counter upon change of severity'. Check that box and it should do exactly that. It simply resets the counter back to 1, but it keeps the alarm history.
I myself am looking for a more comprehensive solution that I can not find the answer to...
There is a Minor alarm that is assigned to an agent with a count of 15. Now the alarm changes to Major. What I need to have happen is for this alarm to have the count reset to 1 (which the 'Reset Suppression counter upon change of severity' option will do, but also unassign the alarm so it appears to be 'new'.
Our agents monitor for unassigned alarms to know what is new, so I either need to be able to create a new alarm (and delete the old) or unassign the existing alarm any time an alrm change severity.
Does anybody have any ideas how to get both of these goals accomplished?
TechnoGeek has a good suggestion, but keep in mind that change will affect all alarms. That may be okay in your environment, but if you want to do this only for certain alarms, you will probably have to use AO profiles. The subject of your post mentioned making a new alarm, and you can do just that from an AO profile. In order to check if there was an actual severity change before generating the new alarm, you may instead need to run a script.
Can you create an AO profile with an assign action and '<none>' as the user? Have it match all alarms on arrival with a count of 0. (I believe that field holds the suppression count rather than the alarm count, but adjust to 1 if necessary.) I think that might get you what you need. If the alarm is actually new, it should not be assigned to anyone anyway, so the fact that it would match the AO profile should be okay.
Retrieving data ...