01.) All alerts for virtualization and the Orion Platform are enabled by default in the Orion Web Console.
02.) To reduce the hassle, you can modify or disable unused alerts.
03.) To modify existing trigger conditions and actions, the best practice would be to create a copy of an alert and customize that copy.
04.) To better monitor issues using alerts, you can use below best practices.
- Adjust thresholds. - Usually, an alert triggers when monitored usage exceeds global or specific VM thresholds.
- Disable alerts. - If an alert is not helpful for your monitoring needs, you can disable it. SolarWinds recommends creating a copy, modify the settings, and disable the original alert.
- Create and customize alerts. - The out-of-the-box alerts cover a range of issues you may want to customize. You can create a copy of an existing alert, disable the original and customize the copy. If you edit an out-of-the-box alert, a message warns what data can be modified or added.
- Set notification actions for specific alerts, not for all alerts. - For large environments, email notification actions on every alert can be overwhelming. You can set email notifications for specific alerts.
- Monitor the Virtualization Summary. - You can use the Virtualization Summary to continuously monitor all alerts. The alerting resources update with every polling. Triggered alerts display in order of severity.
05.) By following the above-mentioned best practices, you will be able to use VMAN more effectively.
