A quick one, dojo - when operating a correlation over base alarms on the DVEs,
is there any quick option to always raise the "Correlated" alarm on the parent element?
Alberto De Luca [DevOps Enabler] Selected answer as best 20th June 2024
Hey Alberto,
I'm wondering what the use case is you try to achieve here, DVE elements are there to isolate logic from a from a bigger element. Is the correlated alarm just for grouping in the alarm console? If so you might not actually want DVE elements in the first place or you can 'disable' the DVE creation under the 'edit element' advanced element setting and disable the DVE creation all together then all the alarms and monitoring are back on the parent.
Kind regards,
Davy
Alberto De Luca [DevOps Enabler] Posted new comment 13th June 2024
Hi Davy,
Indeed I was thinking of this too, but it may require a lot of changes if the DVEs are disabled for this specific implementation.
This is pretty much the context for the correlation:
https://community.dataminer.services/question/correlation-alarm-grouping-options/
Working on a rule that needs to group the occurrences of the same alarm over different rows of the same table in the “parent” element
(Alarm template associated with the parent).
The goal is to trigger an action (notification / new alarm) when all the rows of the DVE present the same alarm condition.
The two DVEs have 7 rows each (14 rows in the MAIN element table), they can work independently (hence the DVE creation, also for different components to be linked automatically in VISIOs).
When the trigger condition is met, it would help to draw the attention of the operator towards the “main/parent” element, e.g. to check the physical chassis.