For Server node-down events, the SolarWinds team has configured two separate alert definitions and expects two incidents to be generated—one for each respective team (Server & Application team). However, due to the current alert aggregation logic based on the message key (which includes networkNodeId and netObjectId), only a single alert is being created.
If we modify the message key to address this, the alert reset event will no longer be able to close all related alerts correctly.
Given this, is there a way to generate separate alerts for each events associated with the same node (i.e., same networkNodeId and netObjectId) without changing the existing message key?
