Embedding an alarm field into the Value massage of a correlated alarm

311 views
1
0 Comments

I have an alarm generated with a field (named FIELD_YYYYY) containing a string (for example XXXXXXX:ID151)

I have created a correlated alarm to capture all the occurrences of this alarm based upon that field (so all occurrences of all alarms with the FIELD_YYYYY and the  contents of that field = XXXXXXX:ID151). It triggers when it receives 10 alarms in 15 minutes. This works well and the value field in the new alarm describes this event.

The value of the FIELD_YYYYY can change so for example, you may get a correlated alarm based on all the alarms with XXXXXXX:ID68

What I would like to do is incorporate the value of that common field into the new alarms ‘Value’ message (so something like ‘There has been a number of alarms for XXXXXXX:ID68’). The correlation rule is grouped on this field.

Similar to a script action such as count(*) >= 2 where you can insert a count of the number of alarms triggering the correlation rule into the new correlated alarm’s Value field (by also selecting the ‘Evaluate value’ option). Is there a similar syntax where you can use to capture the common contents of the field FIELD_YYYYY ??

So, for example, the Value message would say ’There are a number of alarms for XXXXXXX:ID68 (or any other value such as XXXXXXX:ID151)

So possiblbly use the following??

property([alarm].[FIELD_YYYYY])

Many Thanks

Wouter Demuynck [SLC] [DevOps Advocate] Answered question 17th January 2025

1 Answer

0
6.02K 2 Comments

Hi Ken,

You should be able to use [property(Alarm.FIELD_YYYYY)] as a placeholder in the alarm value for a new alarm action.

(also see Script condition functions | DataMiner Docs)

Wouter Demuynck [SLC] [DevOps Advocate] Edited comment 7 days ago
Ken O'Connor [DevOps Member] commented

Thanks Wouter. How would you express it in the Script Condition (under the Rule condition)?

I have the Alarm Value as follows:-

A number of File Validation Alarms have triggered for [property(ALARM.ENTITY.ID)]
Wouter Demuynck [SLC] [DevOps Advocate] commented

Hey Ken, you can refer to alarm properties from script conditions using placeholders like the example below:

Script Condition:

property(Alarm.CustomAlarmProp) == "abc"

=> this will cause the rule to execute its actions as soon as one of the alarms in the bucket has a custom alarm property called "CustomAlarmProp" with "abc" as value

Note that in these expressions, there are no square brackets.

Documentation on the script condition syntax and available functions is here: https://docs.dataminer.services/user-guide/Advanced_Modules/Correlation/Correlation_rule_syntax/Condition_format.html