When we upgraded to 11.5, one alert specifically has stood out so far with having some corruption. We have over 500 alerts so it is going to take quite some time to weed through them all. This one alert was triggering on an interface being down. What we once had was the ${NodeName} within the text of the alert notifications but found after the migration that it no longer worked. I found by replacing it with ${N=SwisEntity;M=Node.DisplayName} it now gives me the node of which the failed interface it on which is much needed when alerting on. I'm hoping that this may be an oversight in coding but feel attention needs to be brought to it as it concerns me about all the other alerts I and Nap have spent a GREAT deal of time in creating. This as well concerns me as I don't have any backup other than the db backup to go to look to compare to ensure that the converted alerts are converted correctly. Hey, I can remember most of the alerts I created but over 500 configurations, I'm not that good. Also in the Reset Condition tab of the Alert, it says The actual trigger condition: Trigger Alert when... I believe it should be Trigger RESET when. causes a bit less confusion as well as it's what causes the reset not the alert trigger. I'm sure I'll have more things to share and frustrations. I realize all can't be perfect but it has to come pretty darn close when our company relies on this software and my job security somewhat depends on it. Now back to finding what else could be jacked up with my baby (Orion).
↧