Hello,
Usually we have a lot of elements with a lot of parameters in their Alarm templates.
For some reasons we have a scenario, when the alarm storm may appears. Term "Alarm storm" in my concern means the SERVER-SIDE event, when we have a lot of alarms. Of cause, in this situation Dataminer Cube should display "Alarm storm" banner but in DMA itself we will have a lot of useless alarms for each parameters per each devices.
My task is to reduce a number of alarms in this case. Imagine, that I can detect, when the "Alarm storm" starts and ends. For example, I can run Automation script time-to-time and get a number of alarms, and if it more than defined - we are running into "Alarm storm" event. After this trigger fired - I will wait for a while and turn this trigger off and go out from "Alarm storm" event.
For this situation, I suggest to define a "important" and "not so important" parameters in all Alarm templates, and once I detect an "Alarm storm" event - I want to disable monitoring for "not so important" parameters. And when I will leave a "Alarm storm" situation - I should enable these parameters.
To do this, I can have two alarm templates for each protocol : "Default template" and "Storm template" and switch it in Automation script for each elements. But this operation is very long and costly.
But each alarm template has "Conditions" per each parameter. So, if it will be possible to use some Global variables in this conditions - it may help me to solve this task.
Is it possible to do? What is your opinion about this feature? I think it should be useful for many customers.
Hi Pieter,
I have about 200 remote sites with Satellite receivers and some other devices on it. Receivers should receive a TV signal from a satellite, convert it to IP interface and stream it locally. Each receiver has dozens parameters to be monitored:
- Link margin
- C/N ratio
- Signal lock
- Modulation
- Frequency
- Symbol rate
- Current bitrate
- ...
When something wrong with satellite downstream (issues with satellite transponder on uplink side, Solar interference, EMF noises, whatever else) - I receive a huge number of alarms per each parameter per each device. Moreover, all other devices, which should receive an IP stream from receiver, also generates an alarms. So, I have 200 receivers (ten parameters per element) and ~500 other devices (15 parameters per element). In this case I receive 10*200+15*500=9500 alarms.
For my users these alarms are useless because users recognize this event as "Alarm storm" and they never use these "atomic" alarms in their workflow. But when my network is not it "Alarm storm" mode - each alarms should be taken into account.
According to my approach - I can define parameters "Signal lock" and "Link margin" as "Important", and all other as "Not so important".
Really, you don't need to control other parameters, if you haven't locked signal, but you should control link margin to "wait" while network is "calming down".
So I have two events:
- Step in to alarm storm : I have similar alarms more than 70% receivers.
- Leave from alarm storm : I have "Signal lock" or "Link margin" alarms less than 10% receivers.
I want to make a driver and create a special element, which should get active alarms (by Timer), and once it detects alarm storm - it will generate it's own alarm "Alarm storm detected in satellite downlink - Critical" and set the Global variable, and this variable may be used as a condition in each alarm template in each driver.