User Problem

Using incident rules to automate incident creation is limiting - there are situations where a user needs a 1:1 correlation between alerts and incidents (as in, every alert will create a new incident), and this is not possible without building a unique incident rule for each possible alert. Also - hardcoding incident rules can be problematic when dealing with changing conditions in the alerts - rules have to be created to match each new potential alert.

Suggested Solutions

Implementing an 'alias' for incidents would allow more flexibility

Current Workarounds

None