Hi all
I have a doubt about an issue raised by the operational team.
Right now in our Dataminer system, when there is a live event from contribution, a service is begin created, with all the devices involved and the parameters in case that need to be displayed.
But right now there is the requests to "silence" or "suppress" the alarms when the service is created, as it will generate a lot of "false-positive" alarms, as the provider of the feed could not provide it from the start, but maybe one hour later or later than that.
But how I could avoid the false positive? I find few parameters I could use as delta to understand when the feed is present or not, but how I could "turn off" the alarm until I not recognize the presence of content?
Hi Marco,
When provisioning the service, is it possible to assign a different alarm template to the elements included in the service? This will help you to suppress these "false-positive" alarms. Once the service is provisioned, you could later trigger an automation script to assign different alarm templates to these elements.
Hope it helps.
HI Marco,
If assigning different alarm templates to an element is not an option, have you already checked the possibility of masking the alarms?
Yeah mask could be a solution, could be achive in case via correlation rule? so I can filter only on the services I need to check
Hi Miguel, yeah is something I tried, but the services could share the same elements, so if I try to turn off the alarm template for service A that is just started, I will also turn it off in service B that is already live.
So this is not a valid solution.
I think about to just "hide" the alarms as they are showed via a LCA and GQI, so in case just don't fetch the alarms for event that are not live