Catarina Grilo
User info
| First name | Catarina |
| Last name | Grilo |
DevOps Program
| Acquired rank |
Advocate
|
| Points progress |
4200
DevOps Points
|
 Here are a few tips to level up your DevOps game and unlock an arsenal of perks and benefits.
|
|
| DevOps attestation | Request your attestation ID and expiry date |
Achievements
|
|
Questions asked
Answers given
Hi Joshua, According to our documentation (Dynamic virtual elements | DataMiner Docs), elements that allow DVE creation cannot be part of a redundancy group: However, you can create redundancy groups...
View Question
Hi Sevil, Each folder corresponds to a database table (e.g., “alarm_property” or “data”) that you configured in the offload. See the example below: For more information, see: System...
View Question
Hi Ramon, Currently, the audible alerter in the alarm console cannot be directly configured to differentiate between specific alarm severities. For further details, please refer to the following guide:...
View Question
Hi Joaquim, It appears that the Alarm Storm Protection mode is active in your system due to a high volume of alarms for two specific parameters: "Parameter Invalidity Checking" – currently showing...
View Question
Hi Simon, At this time, there isn't an option to completely disable the display of alarm history, as outlined in History tracking | DataMiner Docs. However, you can minimize the number of alarms...
View Question
Hi Jeroen, This is a known issue, and a release note already exists to address it. The fix will be included in Main release 10.4.0 [CU14] ; 10.5.0 [CU2] and Feature release 10.5.5. Reference: RN42546....
View Question
Hi Jesus, If I understand your question correctly, you're looking for the full history of an alarm, the entire alarm tree, correct? If that's the case, you can use GetAlarmHistoryV2 | DataMiner Docs to...
View Question
Hi Nigel, I looked into the documentation on aggregation (About aggregation rules | DataMiner Docs) and found that aggregation seems to be calculated based on real-time parameter values. Since replication...
View Question
Hi Nick, While alarming a discplay key column is not allowed, as referenced in our docs Display keys | DataMiner Docs: There should be no issue referencing a display key in alarm conditions. However,...
View Question
Hi Dojo team, especially Carys, I managed to resolve the issue by manually forcing a sync of the file using ClientTestTool. Here’s what I did: Opened the ClientTestTool. Connected to the DMA containing...
View Question
Hi Min, Based on your screenshot, there are two separate alarms: one for "param 1" and another for "param 2." These alarms will be evaluated independently. Since your condition requires both "param...
View Question
Hi Dave, I believe this change is only reflected in the log file of the element itself. There is no corresponding information event, for example. However, if you go to Cube > System Center > Logging...
View Question
To trigger the rule when two specific alarms occur, you'll need to use the rule condition instead of the alarm filter. In the rule condition, add a script condition, and then include the filter conditions...
View Question
Hi Ramesh, The behavior you're seeing in the Alarm Console is expected. When using a filtered alarm tab and viewing history alarms where the correlated alarm is already closed, you'll only see the correlated...
View Question