R12.1 Project-2025Sep08
Example for Incident Merging
Define settings to merge incidents according to different scenarios.
These issues are common in a user’s 3rd party integrated system:
- The interface status of a device changes to a down state. If multiple interfaces on a device change to ‘down’ within 30 minutes, trigger automations and then merge their results into a single NetBrain incident.
- The BGP neighbor status on a device changes to down.
- Hosts become unreachable.
- CPU usage is too high on a device. Issues of high CPU usage occurring within 10 minutes are considered the same.
Define the settings based on the scenario.
- Define a policy for issue 1.
- Define a policy named Interface Down with these settings:
- Define a policy for issue 4. To prevent redundant automation triggers, create a policy named CPU Usage is High with the following settings:
- Each issue in 2 and 3 is distinct and independent, so the user doesn’t need to define policies for them.