Hi Dojo,
when using the "audible alert" in the DataMiner alarm console, we experience a strange behaviour: only the settings of the active alarms tab are showing any effect. Despite the fact that the settings can be set individualy for every single tab in the alarm console, only the alert configured for the first tab seems to be active and overrules all other configurations.
Is this expected behaviour (to us it isn't, at least), or is this something that needs to be fixed? Anything that needs to be taken into account regarding the configuration?
Thanks!
Hi Dojo,
well, the solution was simple: everything works as designed, but we only applied quick filters instead of proper filtering in the individual alarm tabs. Therefore the alarms in the different tabs have been the same, just the displayed selection of alarms was altered.
Once we applied real filtering (and not only quick filters), the audible alerts worked accordingly. So no issue at all here. 🙂
Hi Pieter,
yes, everything fine indeed! Thanks a lot, best wishes to you as well! 🙂
Hi Nils,
I did a quick test on my local agent to see if I could notice any defect. I have configured a audio alert on my active alarms that should only play once and then also configured a repeating audio alert on a alarm tab page filtered on a specific element.
When an alarm enters in both tab pages, I hear the two sounds and one stops after one routine, the second one continues as configured.
So I seem to be able to configure the audio alerts on both my active and custom alarm tab page, not sure if you can share more details about your configuration or if we need to proceed with a support ticket maybe?
Hi Pieter,
good to hear from you!
Thanks a lot for your response and looking into this. After receiving no answer to this question for a while, I already opened a task a few days ago. So your colleagues from TechSupport picked this up.
Anyway, it seems that we are having a hard time to actually reproduce the issue. 😮 As of now, we are checking it out again and will come back to your colleagues. Best case, this has resolved itself mysteriously. 😉
Hi Nils,
Good to hear that our support team was helping your further.
All the best!
Ok great, happy to hear this is resolved now. Hopefully the current design also fits with your use case. Best regards Nils and a happy 2025!