Enhance topology correlation by providing options to filter the candidate alerts for correlation from both connected devices.

Currently topology templates are defined based on connected devices/interfaces. Even though the correlation based on topology is time bound, there is no option to filter which alerts to be part of topology grouping similar to scope grouping.

In the network, there will be many alerts which are generated from device at the same time which may be service impacting but not necessarily to be part of same correlation. In the legacy Netcool system, the correlation rules are defined based on alert properties and the time duration. This approach restricts the over grouping of alerts and also ensuring only candidate alerts are part of correlation. 

In topology correlation let's say we have Device A with 20 alerts which came in 10:00 AM, the device B which is connected to Device A and bound by topology template got 10 alerts, then those 30 alerts will be part of topology grouping and get correlated. 

 But for an operator, out of 30 alerts, only 5 or 6 alerts should only be part of correlation, as other seems to be not important or are not candidate for the correlation.  This can be achieved by filtering based on alert properties and the connected device.

The option to choose or filter alerts should be added in such a way that the new feature should help user to enable the option to add conditions based on alerts while creating topology correlation.