After you create a counter monitor, you assign (target) it to one or more server instances. The counter monitor looks for changes in attribute values only on the servers to which it has been targeted.
Note: To temporarily stop this counter monitor from generating traps, un-target it from all servers by deselecting them on the Servers tab.
To target counter monitors:
Note: When you assign a counter monitor to a server, you deploy a JMX listener and filter to the server. The listener forwards a notification to the WebLogic SNMP agent only if an event matches the criteria in the counter monitor.
For
example, if you create a counter monitor that
observes the AcceptBacklog
attribute of ServerA's Server
MBean, and if you target this counter monitor to
ServerB, the counter monitor on ServerB will never
generate a trap, because ServerB does not have
access to the configuration data of
ServerA.