This content has been marked as final. Show 6 replies
Create different Incident Rules for the different target types. Host targets in GroupA -> HostTeamA, DB targets in GroupA -> DBTeamA
Check out this whitepaper for more details on how to customize the groups and incident rules to fit your enterprise. http://www.oracle.com/technetwork/oem/sys-mgmt/wp-em12c-monitoring-strategies-1564964.pdf
ok, but I think that is not yet a solution to the problem.
We have GroupA, GroupB, GroupC and so on, different target types are belonging to these groups.
GroupA is interested in receiving "load/cpu" related notification which is monitored at the host level.
GroupB does not want to receive this "load/cpu" metric but is also having a database on the same host as GroupA.
Should we still be able to accomplish this using Incident Rules?
Edited by: user5554585 on Feb 22, 2013 2:16 AM
What properties are you using for your administration hierarchy? When you say that you want to send notifications to multiple groups are you talking about EM Groups or groups of administrators? You can specify which groups (as in administrators) get certain notifications by creating rules that specify the events that you are in interested in e.g. load/cpu utilization and then apply those rules to the Admin Group.
Thanks for the update.
Ok, looks like at incident rule level you can leave out certain objects and so avoiding a notification to a particular EM Group, you should create rules based on the requirement for each Group.
But I also wonder what you would do in case you are monitoring the filesystems on a host having databases belonging to more than one EM Group.
GroupA managing DB1 does not want to receive filesystem alerts from DB2 belonging to GroupB, (DB1 & DB2 running on the same host)
I've tried to understand how that could be accomplished through Rules. When I edit "Filesystems, Filesystem Space Available (%)" I can select add objects by manually selecting from all available mountpoints which is not very helpful.