Hello,
I’m wondering if there is a way to establish a relationship between the primary key and foreign key based on specific conditions for a single alarm.
To provide some context, I have two tables: the “node” table and the “amplifier” table. It’s important to note that multiple amplifiers can be linked to a single node.
I’m interested in suppressing alarms for amplifiers, but only under two conditions:
- When the number of CM in the node table exceeds 2.
- When the percentage of CM in the node table reaches 100%.
My question is whether these two conditions alone are sufficient to suppress the alarms at the amplifier level, or if I need to include a relationship between the tables within the conditions.
Sergio,
If the driver has the correct configuration for relations and foreign-key options and both of these metrics are in a parameter value this shouldn’t be a problem.
See the documentation on how to configure a condition:
Configuring alarm templates | DataMiner Docs
However if I understand the use case correctly the ‘count’ mentioned in the first condition probably isn’t a parameter value. We currently don’t support logic based on amount on counting the amount of resolved foreign key based relations.
FK to itself is currently not supported for conditional monitoring so if you define it, I believe undefined behavior will be seen since we do not test it.
Hi Davy,
And what if there is a recursive table. The amplifier table has a FK to itself. How would the relation be?