Hi, is there a way to configure Dataminer to generate a critical alarm condition when a given element goes into comms-loss and also if an element remains in comms-loss for longer than a pre-defined length of time?
Ben Vandenberghe [SLC] [DevOps Enabler] Selected answer as best 22nd December 2020
Hi Paul,
You can achieve this using correlation.
Below you'll find a sample configuration.
Paul Camus [DevOps Member] Posted new comment 22nd December 2020
And in a similar fashion, you could also trigger a similar extra notification probably if a managed element goes too many times in and out of time-out in a specific timespan.
Hi Paul,
You can further finetune the filter, (where we currently only filter for timeout alarms) to also filter for a specific protocol, element, view, etc
Hi, thank you once again for the useful feedback
Hi Ive, thank you for getting back so quickly.
Once created can such a correlation rule (like your example) be set to only be active on selected elements / views or perhaps only be associated with selected alarm templates?