Servers: Services: SNMP

Column Display Related Tasks Related Topics

This page summarizes the SNMP attribute changes, log filters, and SNMP monitors that have been targeted to this server.

If you target SNMP agents to individual Managed Servers, you do not need to target attribute changes, log filters, and SNMP monitors to a server. An SNMP agent on a Managed Server monitors only the resources on its host Managed Server.

If you want to use an SNMP agent on the Administration Server to monitor all servers in the domain, then you must target attribute changes, log filters, and SNMP monitors to individual servers.

Attribute changes configure an SNMP agent to send a notification immediately after a configuration attribute is changed in any way. For example, you can configure an attribute change that sends a notification whenever a server's listen address changes.

A log filter enables WebLogic Server to generate notifications when subsystems or applications generate log messages.

WebLogic SNMP monitors poll WebLogic Server MBeans at a specified interval to check for the occurrence of conditions or the crossing of thresholds. When a monitor detects the specified condition, it sends a notification to the configured trap destinations. WebLogic Server supports three types of monitors:

A string monitor periodically polls an attribute whose value is a string and generates a notification if the attribute value matches a string that you specify. Alternatively, you can specify that the monitor generates a notification if the attribute value does not match your string.
A gauge monitor indicates whether an attribute is operating within a specific range.
A counter monitor indicates whether an attribute value is above a specific threshold.

Column Display

Name	Description
Name	The name that you specified when you created the attribute change.
Monitored MBean Type	The MBean type that defines the attribute you want to monitor. Do not include the `MBean` suffix. For example, specify `Server` to monitor a ServerMBean. WebLogic Server does not support using Attribute Change notifications to monitor run-time attributes. Runtime MBeans always include the word `Runtime` in their names. For example, the `ServerRuntime` MBean provides access to runtime attributes while the `Server` MBean provides access to configuration attributes. To monitor changes in an MBean that includes `Runtime` in its name, use a String Monitor, Gauge Monitor, or Counter Monitor. MBean Attribute: `SNMPAttributeChangeMBean.AttributeMBeanType`
Monitored MBean Name	The name of the MBean instance that you want to monitor. If you leave the name undefined, WebLogic Server monitors all instances of the MBean type that you specify in Monitored MBean Type. Do not enter the full JMX object name of the MBean instance. Instead, enter only the value that you provided when you created the instance. To create unique MBean object names, WebLogic Server encodes several name-value pairs into each object name. One of these pairs is `Name=name`, and this is the value that you enter for MBean Name. For example: `"MedRec:Name=MedRecServer, Type=ServerRuntime"` In the previous example, specify `MedRecServer` as the name of the MBean instance. MBean Attribute: `SNMPAttributeChangeMBean.AttributeMBeanName`
Monitored Attribute Name	The name of the attribute that you want to monitor. This attribute must be in the WebLogic Server MIB. MBean Attribute: `SNMPAttributeChangeMBean.AttributeName`
Enabled Servers	This attribute is applicable only when the SNMP Agent is running on the Admin Server of a WebLogic Domain. The EnabledServers attribute allows the users to limit the scope of the monitored data sources to the specific named Servers. The EnabledServers list is ignored when the SNMAgentDeploymentMBean is targeted to a Managed Server. In the case of a Managed Server the SNMP Agent only looks at the data available in the WebLogic Server where the SNMP Agent is deployed. For traps based on MBean attributes the SNMP Agent refers to the Domain Runtime MBean Server when it is running on the Admin Server and the Runtime MBean Server when it is deployed to a Managed Server. In the case of `SNMPJMXMonitorMBean` and `SNMPAttributeChangeMBean` the `MonitoredMBeanType` and `MonitoredMBeanName` attributes specify the type and name of a WebLogic Server MBean for which the trap will be setup. MBeans that meet the Type and Name criteria are qualified to set the trap on. The EnabledServers attribute allows a user to specify additional criteria based on the Location of an MBean when the SNMP Agent is targeted to the Admin Server. MBeans whose Location matches one of the Servers in the EnabledServers list are considered eligible for the trap to be generated for a corresponding JMX notification. When the EnabledServers attribute is not specified all MBeans whose Type and Name match are considered as valid sources for the SNMP trap. In the case of `SNMPLogFilterMBean` the EnabledServers attribute allows a user to specify the Servers in the Domain whose log messages will be monitored when the Agent is running on the Admin Server. When EnabledServers is not specified for an Agent running on the Admin Server log messages on all Managed Servers in the domain are monitored for sending traps. This attribute is not applicable when the SNMP Agent is targeted to a Managed Server, in this case the traps are sent based on log messages generated by the respective Managed Server where the Agent is deployed. MBean Attribute: `SNMPAttributeChangeMBean.EnabledServers`

Column Display

Name	Description
Name	The name that you specified when you created the log filter.
Severity Level	The minimum severity of a message that causes a WebLogic Server SNMP agent to generate a notification. MBean Attribute: `SNMPLogFilterMBean.SeverityLevel`
Subsystem Names	A list of subsystems whose messages are selected by this log filter. If none are specified, messages from all subsystems are selected. MBean Attribute: `SNMPLogFilterMBean.SubsystemNames`
User IDs	A list of user IDs that causes a WebLogic Server SNMP agent to generate a notification. Every message includes the user ID from the security context in which the message was generated. If the user ID field for a message matches one of the user IDs you specify in the filter, WebLogic Server generates a notification. If this log filter doesn't specify user IDs, WebLogic Server can generate a notification for messages from all user IDs. MBean Attribute: `SNMPLogFilterMBean.UserIds`
Message IDs	A list of message IDs or ID ranges that cause a WebLogic Server SNMP agent to generate a notification. If no IDs are specified, this filter selects all message IDs. Example list: 20,50-100,300 MBean Attribute: `SNMPLogFilterMBean.MessageIds`
Message Substring	A string that is searched for in the message text. Only messages that contain the string are selected. If a string is not specified, all messages are selected. MBean Attribute: `SNMPLogFilterMBean.MessageSubstring`
Enabled Servers	This attribute is applicable only when the SNMP Agent is running on the Admin Server of a WebLogic Domain. The EnabledServers attribute allows the users to limit the scope of the monitored data sources to the specific named Servers. The EnabledServers list is ignored when the SNMAgentDeploymentMBean is targeted to a Managed Server. In the case of a Managed Server the SNMP Agent only looks at the data available in the WebLogic Server where the SNMP Agent is deployed. For traps based on MBean attributes the SNMP Agent refers to the Domain Runtime MBean Server when it is running on the Admin Server and the Runtime MBean Server when it is deployed to a Managed Server. In the case of `SNMPJMXMonitorMBean` and `SNMPAttributeChangeMBean` the `MonitoredMBeanType` and `MonitoredMBeanName` attributes specify the type and name of a WebLogic Server MBean for which the trap will be setup. MBeans that meet the Type and Name criteria are qualified to set the trap on. The EnabledServers attribute allows a user to specify additional criteria based on the Location of an MBean when the SNMP Agent is targeted to the Admin Server. MBeans whose Location matches one of the Servers in the EnabledServers list are considered eligible for the trap to be generated for a corresponding JMX notification. When the EnabledServers attribute is not specified all MBeans whose Type and Name match are considered as valid sources for the SNMP trap. In the case of `SNMPLogFilterMBean` the EnabledServers attribute allows a user to specify the Servers in the Domain whose log messages will be monitored when the Agent is running on the Admin Server. When EnabledServers is not specified for an Agent running on the Admin Server log messages on all Managed Servers in the domain are monitored for sending traps. This attribute is not applicable when the SNMP Agent is targeted to a Managed Server, in this case the traps are sent based on log messages generated by the respective Managed Server where the Agent is deployed. MBean Attribute: `SNMPLogFilterMBean.EnabledServers`

Column Display

Name	Description
Name	The name that you specified when you created the SNMP monitor.
Type	The type of SNMP monitor.
Monitored MBean Type	The MBean type that defines the attribute you want to monitor. Do not include the `MBean` suffix. For example, `ServerRuntime`. MBean Attribute: `SNMPJMXMonitorMBean.MonitoredMBeanType` Changes take effect after you redeploy the module or restart the server.
Monitored MBean Name	The name of the MBean instance that you want to monitor. If you leave the name undefined, WebLogic Server monitors all instances of the MBean type that you specify in Monitored MBean Type. If you target SNMP agents to individual Managed Servers, make sure that the MBean instance you specify is active on the Managed Servers you have targeted. For example, if you specify `MServer1` as the name of a ServerRuntimeMBean instance, this monitor will only function if you target an SNMP agent either to the Administration Server or to a Managed Server named `MServer1`. Do not enter the full JMX object name of the MBean instance. Instead, enter only the value of the object name's `Name=name` name-value pair. To create unique MBean object names, WebLogic Server encodes several name-value pairs into each object name. One of these pairs is `Name=name`. For example: `"MedRec:Name=MedRecServer, Type=ServerRuntime"` In the previous example, specify `MedRecServer` as the name of the MBean instance. MBean Attribute: `SNMPJMXMonitorMBean.MonitoredMBeanName` Changes take effect after you redeploy the module or restart the server.
Monitored Attribute Name	The name of an MBean attribute to monitor. This attribute must be in the WebLogic Server MIB. MBean Attribute: `SNMPJMXMonitorMBean.MonitoredAttributeName` Changes take effect after you redeploy the module or restart the server.
Polling Interval	The frequency (in seconds) that WebLogic Server checks the attribute value. MBean Attribute: `SNMPJMXMonitorMBean.PollingInterval` Minimum value: `1` Maximum value: `65535` Changes take effect after you redeploy the module or restart the server.
Enabled Servers	This attribute is applicable only when the SNMP Agent is running on the Admin Server of a WebLogic Domain. The EnabledServers attribute allows the users to limit the scope of the monitored data sources to the specific named Servers. The EnabledServers list is ignored when the SNMAgentDeploymentMBean is targeted to a Managed Server. In the case of a Managed Server the SNMP Agent only looks at the data available in the WebLogic Server where the SNMP Agent is deployed. For traps based on MBean attributes the SNMP Agent refers to the Domain Runtime MBean Server when it is running on the Admin Server and the Runtime MBean Server when it is deployed to a Managed Server. In the case of `SNMPJMXMonitorMBean` and `SNMPAttributeChangeMBean` the `MonitoredMBeanType` and `MonitoredMBeanName` attributes specify the type and name of a WebLogic Server MBean for which the trap will be setup. MBeans that meet the Type and Name criteria are qualified to set the trap on. The EnabledServers attribute allows a user to specify additional criteria based on the Location of an MBean when the SNMP Agent is targeted to the Admin Server. MBeans whose Location matches one of the Servers in the EnabledServers list are considered eligible for the trap to be generated for a corresponding JMX notification. When the EnabledServers attribute is not specified all MBeans whose Type and Name match are considered as valid sources for the SNMP trap. In the case of `SNMPLogFilterMBean` the EnabledServers attribute allows a user to specify the Servers in the Domain whose log messages will be monitored when the Agent is running on the Admin Server. When EnabledServers is not specified for an Agent running on the Admin Server log messages on all Managed Servers in the domain are monitored for sending traps. This attribute is not applicable when the SNMP Agent is targeted to a Managed Server, in this case the traps are sent based on log messages generated by the respective Managed Server where the Agent is deployed. MBean Attribute: `SNMPJMXMonitorMBean.EnabledServers`
Agent Name	The user-specified name of this MBean instance. This name is included as one of the key properties in the MBean's `javax.management.ObjectName`: `Name=user-specified-name` MBean Attribute: `SNMPAgentMBean.Name`

Related Tasks

Administration Console Online Help

Servers: Services: SNMP

Column Display

Column Display

Column Display