Last updated on SEPTEMBER 23, 2016
Applies to:Enterprise Manager Base Platform - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Reducing the number of email notifications for an Incident RuleSet on an Administrative Group caused by alerts during an outage is described in this article.
Without such an improvement to the notification policy, if a SOA managed server goes down (for whatever reason), it is very difficult to determine if any other incidents occurred at the same time because the default notification policy floods intended recipients with numerous emails.
For an Incident RuleSet on an Administrative Group consisting of the entire WebLogic Stack, EM sends many emails for specific events applicable to a Target Group.
Take the following scenario as an example:
Perform a manual shutdown of a SOA server through the WLS Admin Console without blacking out any targets in EM prior to doing so. Many email notifications will result because of the way that this shutdown is handled. EM alerts on all of the components that are being shut down: the composites, email driver, soa-infra deployment and finally the managed server itself.
Of course, there is a need to be alerted on any and all of these components when they go down individually. For convenience, though, email notifications should only occur at the top-most component when there is a shutdown/outage on a composite target.
An improved notification policy would be to notify the top level items that alert on shutdown. In the example scenario, where a managed server is being shutdown, only notify for the SOA managed server, not the hundreds of components that make it up as well.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms