User info
First name | Bram |
Last name | Devlaminck |
DevOps Program
Points progress |
![]()
3687
DevOps Points
|
![]() |
|
DevOps attestation | Request your attestation ID and expiry date |
Achievements
|
Questions asked
Answers given
Hi, To make sure that other people are aware: An internal investigation was done behind the scenes as part of a related task, and it turned out the issue was caused by a proxy configuration, not the...
View QuestionHi Stefan, The warning that you are seeing is generated by the SLWatchdog process. Your protocol most likely has some group that is being executed that contains your QAction (correct me if this is not...
View QuestionHi Simon, Instead of undocking the whole alarm console, you could undock each of the separate tabs (by dragging them "away" from the console), and then choose "dock to workspace" To still have tabs, choose...
View QuestionHey, The filtering also works as a fall-through chain. You'll have to make sure that the most strict rule is at the top. In the case of your screenshot: the top rule allows everything, so whatever you...
View QuestionHi Maxime, The answer (from Tobe Deprez) on the following DOJO post is probably what you are looking for: https://community.dataminer.services/question/show-message-in-active-alarms-using-automation-script/...
View QuestionHi Aditiben, Could you please provide some more information about the function file you are mentioning? Perhaps a screenshot of another connector where you have such a file? My best guess at the moment...
View QuestionHi Ramesh, You should be able to achieve this with a combination of a correlation rule that groups the alarms per service, and then an automation script to do the actual "combining" into a new alarm that...
View Question