Hi, I see where Joe is coming from with the term 'Alarm Shelving', but I think it is a term of art in the alarm management world (entirely random example provided by duckduckgo... https://www.exida.com/Blog/Alarm-Shelving-Relieve-the-Symptoms-of-Nuisance-Alarms). Actually, I found the term to be quite evocative of the process. His point about the impact on server resources is worth exploring. And finally, yes, it seems to me that shelving and suppression of notifications seem to be approaching orthogonal. That is, suppression of notifications is not the same as suppression of alarms. > Broadly speaking, I found the term "Alarm Shelving" to > be confusing. You do define this, but it is not something that many operators > are familiar with. I had originally thought alarm suppression was better, but > after I read more, I see what you're trying to do with this. > > Additionally, some of the features like alarm-history and alarm-shelving have a > potential operational impact with respect to local server resources, and > perhaps that's worth calling out. > > Finally, I can see where it might be desirable to suppress alarm notifications > without shelving them per se. That is, the alarm remains in the list, but > notifications are not sent. That doesn't seem possible, and I'm wondering if > it's worth considering. Cheers, Adrian -- Want to buy a signed copy of a book of fairy stories for adults of all ages? Send me an email and I'll bring one to Prague for you. "Tales from the Wood" "More Tales from the Wood" "Tales from Beyond the Wood" https://www.feedaread.com/profiles/8604/
