SNMP Agents: Configuration: Log Filters
Column Display Related Tasks Related Topics
A log filter enables a WebLogic Server SNMP agent to generate notifications when subsystems or applications generate log messages.
Subsystems and deployable modules (such as applications) on a WebLogic Server instance generate log messages to communicate status or other operational data. The data within a log message is divided into fields that you can use for filtering purposes. For example, each message contains a severity field that indicates the potential impact of the event that generated the message.
Each server saves these messages in a local log file and then broadcasts them as JMX notifications. You can create SNMP log filters that cause a WebLogic Server SNMP agent to listen for these messages. When the agent receives a message that matches the filtering criteria, it generates a notification and sends the notification to the configured trap destinations.
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name
The name that you specified when you created the log filter.
The minimum severity of a message that causes a WebLogic Server SNMP agent to generate a notification.
A list of subsystems whose messages are selected by this log filter. If none are specified, messages from all subsystems are selected.
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.
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
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.
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
MonitoredMBeanNameattributes 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
SNMPLogFilterMBeanthe 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.
- Create SNMP log filters
- Target SNMP log filters
- Delete SNMP log filters
- Stop generating notifications