Too many e-mail alerts are being generated
PATROL is generating too many e-mail messages, or too many notifications in general or you are receiving notifications for events that are not important to you.
Explanation | Solution |
|---|---|
Parameters and thresholds need tuning. | Begin baselining and adjusting parameter thresholds. Review the e-mail alerts to determine which parameters are generating alerts. Then adjust the parameter thresholds, deactivate threshold ranges, or deactivate parameters, as necessary. You can make these changes on one remote agent and then use the PATROL Configuration Manager to deploy these changes to other agents. |
Blackout periods are needed. | If you are receiving alerts because systems are down for maintenance, you should configure blackout periods that specify when alerts are not generated. For more information, see the PATROL KM for Event Management online documentation portal. |
The rule /AS/EVENTSPRING/ALERT/ arsAction is set to 4. | Set the rule /AS/EVENTSPRING/ALERT/arsAction to 0. If the arsAction rule is set to 4 for all PATROL objects, notifications are sent for all events. Instead, you may want to disable notification for all PATROL objects, by setting /AS/EVENTSPRING/arsAction to 0 at the remote agent. Then, enable notification only for the desired applications, instances, or parameters. When you enable notification for a specific PATROL object, the following configuration variable is created: /AS/EVENTSPRING/ALERT/object/arsAction |