Hi Dojo - posting this question as I'm looking into the different possibilities to aggregate alarms in a DMS: adding below the ones I can think of - but would there be any possibility to use any kind of "aggregation rule" too? I seem to recall that's a different thing - so I'm also looking into any other feature that is present by default in a standard DMA with automation & correlation engines

Root Cause Analysis:
once in place, I believe this could be used to trim down the list of active alarms presented in console;

Correlation Rules:
e.g. to give just 1 alarm on a view or a service when many of the elements (in the service or the view) have different alarms raised within a given sliding window;

Any other possible aggregation mechanism that can be put in place?
Sorry if this seems quite a basic question - just keen to consider all of the possible options.
Any steer will be helpful.
Thanks