We're exploring the options to have alarms to identify if the expected configuration is correct/incorrect for a specific event (we're talking about amount of Audio channels, subtitle components, aspect ratio,...)
Every event could have different configurations (what's normal for one event is an alarm for another), one option we're exploring is do dynamically (create/) assign the alarm template to the right element.
However question that rises is how performant would this be?
Does an alarm template take seconds, tens of seconds, ... and how does this scale?
Is this dependent of the amount of parameters on the element, amount of monitored parameters in the template, ...?
Another option we explore is to have an additional element that gets the values from the probe element and then calculates if eveything is ok or not using a "fixed" alarm template and a fixed amount of configurations to check
Hi Tim,
Creating the alarm itself should not be a costly operation but assigning it to existing elements could indeed take some time and it will vary according to the amount of alarmed parameters as DataMiner will need to recalculate the alarm state for all of those and the elements and views and potentially services involved in the process.
I do not know of the exact metrics for your use case but some of the ones we have available in this docs page DataMiner metrics | DataMiner Docs and its subpages should be a good indication of what to expect.
If you look into 14 of Alarm benchmarks | DataMiner Docs you should see that it takes a few seconds to create 1000 alarms with addrows operations. This is not exactly what you have as a use case but it can give a ballpark.
I hope this can help.