I tried to correlate Alarms of KVARTAs and group them by a Value (frequenz or transponder).
But "Alarm Grouping" seems have too general options, because I need to state a specific Tablevalue (see "KVARTA Alarm Table" screenshot "Name"), to work probably. With using "Group these alarms by table index" doesn't work, because they are not matching.
So, is there a way to be more specific with "Alarm Grouping"?
- Screenshot: Correlation rule
- Screenshot: KVARTA Alarm Table
Two options which involve some (minor) driver development.
- Let the driver add a 'Transponder' or 'Frequency' alarm property to each generated alarm, and then use this property to group within the correlation rule
- Add an additional 'Transponder' or 'Frequency' table to the driver, which aggregates the state from the 'Active Alarm Table' per Transponder/Frequency, and use that state to generate alarms on
Let's see if there might be other ideas that do not involve development...
Yes, that is the solution.
I added an information template, added the alarm property with the value “Name” on the “Alarm” Table parameter & grouped alarms by property value “Alarm.Frequenz” in the correlation rule.
You can add custom alarm properties using an information template.
This will give you the desired properties to finetune your alarm grouping.
More details on information templates can be found in the DataMiner help:
Basic DataMiner functionality -> Protocols and Templates -> Information Templates -> Creating an information template.