Does anyone know how to set/change the suppression key for a sqlserver profile?
I think suppression keys are hardcoded in a lot of probes. You can definitely change them in some, but I do not see that option in all of them. I looked at sqlserver.cfg to see if suppression keys might be specified there, but I did not find anything. I was not surprised because in that probe I think they need to be built on the fly. But there was still a possiblity that part of the suppression key might have been in the config.
Why do you want to change a suppression key in the sqlserver probe? I am very curious...
Each of these profiles monitors a single sql server instance for the ‘last backup’ checkpoint for every database on that server. Whether one database goes beyond the threshold or all go beyond the threshold on that server, I want to see one alert for each server that has a DB that has not been backed up in 24 hours. As it is currently configured, I will see an individual alert for every db under every profile.
The alarm messages appear to be similar enough that the NAS Message Suppression should just increment the alarm instead of issuing separate alarms. However, since the suppression key is unique for each alarm, I suspect this is why they are not being consolidated.
That is exactly why the alarms are not being suppressed. The message text is only used for suppression when there is no suppression key.
It looks like you can disable the use of the suppression key in the NAS. I would not recommend that though. It would have a lot of side effects.
You can change the suppression key in incoming alarm messages by using a custom pre-processing rule with a Lua script. That is probably your best bet. The other option is to make all of those alarms invisible but then create a trigger that goes active when any of those alarms are present. Then you can make an alarm based on that trigger, so you only see the one alarm no matter how many made the trigger active.
Thanks Keith, I appreciate the help! I think I will go the pre-processing route.
Retrieving data ...