SMNP --> Traps --> Log Filter --> General

SMNP --> Traps --> Log Filter --> General

Tasks Related Topics Attributes

Overview

Use this tab to set up the WebLogic SNMP agent to listen for log messages that a server instance broadcasts. When the agent receives a message, it generates an SNMP log notification trap.

Tasks

Configuring a Notification Log Filter

Related Topics

WebLogic SNMP MIB Reference
WebLogic SNMP Management Guide

Attributes

Attribute Label

Description

Value Constraints
Name The name of this log filter. Each log filter within a domain must have a unique name.The name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the log filter. After you have created a log filter, you cannot change its name. Instead, clone the filter and provide a new name for the clone. For more information, refer to Cloning Configuration Objects.MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: Name

Severity Level The minimum severity of a message that causes WebLogic Server to generate a trap. The ascending order of severities:
INFO. Used for reporting normal operations.

WARNING. A suspicious operation or configuration has occurred but it may not have an impact on normal operation.

ERROR. A user error has occurred. The system or application is able to handle the error with no interruption, and limited degradation, of service.

NOTICE. A warning message. A suspicious operation or configuration has occurred which may not affect the normal operation of the server.

CRITICAL. A system or service error has occurred. The system is able to recover but there might be a momentary loss, or permanent degradation, of service.

ALERT. A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem.

EMERGENCY. The server is in an unusable state. This severity indicates a severe system failure or panic.
If you enter INFO, then WebLogic Server can generate a trap when a server instance prints a message of any severity.MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: SeverityLevel Default: WARNING
Subsystem Names Defines a list of subsystems whose messages are selected by this filter. If none are specified, then WebLogic Server can generate a trap when any subsystem prints a message.MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: SubsystemNames

User Ids Defines a list of user IDs that causes WebLogic Server to generate a trap. 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 trap. If no IDs are specified, WebLogic Server can generate a trap for messages from all user IDs.MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: UserIds

Message Ids Defines a list of message IDs or ID ranges that cause WebLogic Server to generate a trap. To see the ID of a message, view a server's message log. For more information, refer to Viewing Server Logs from the Administration Console.If no IDs are specified, this filter selects all message IDs.Example list: 20,50-100,300MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: MessageIds

Message Substring Defines 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: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: MessageSubstring

Enabled Servers Defines a list of servers whose messages can cause WebLogic Server to generate a trap.If no server is specified, no traps will be generated.MBean: weblogic.management.
configuration.
SNMPLogFilterMBeanAttribute: EnabledServers

Attribute Label	Description	Value Constraints
Name	The name of this log filter. Each log filter within a domain must have a unique name.The name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the log filter. After you have created a log filter, you cannot change its name. Instead, clone the filter and provide a new name for the clone. For more information, refer to Cloning Configuration Objects.MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: Name
Severity Level	The minimum severity of a message that causes WebLogic Server to generate a trap. The ascending order of severities: INFO. Used for reporting normal operations. WARNING. A suspicious operation or configuration has occurred but it may not have an impact on normal operation. ERROR. A user error has occurred. The system or application is able to handle the error with no interruption, and limited degradation, of service. NOTICE. A warning message. A suspicious operation or configuration has occurred which may not affect the normal operation of the server. CRITICAL. A system or service error has occurred. The system is able to recover but there might be a momentary loss, or permanent degradation, of service. ALERT. A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem. EMERGENCY. The server is in an unusable state. This severity indicates a severe system failure or panic. If you enter INFO, then WebLogic Server can generate a trap when a server instance prints a message of any severity.MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: SeverityLevel	Default: WARNING
Subsystem Names	Defines a list of subsystems whose messages are selected by this filter. If none are specified, then WebLogic Server can generate a trap when any subsystem prints a message.MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: SubsystemNames
User Ids	Defines a list of user IDs that causes WebLogic Server to generate a trap. 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 trap. If no IDs are specified, WebLogic Server can generate a trap for messages from all user IDs.MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: UserIds
Message Ids	Defines a list of message IDs or ID ranges that cause WebLogic Server to generate a trap. To see the ID of a message, view a server's message log. For more information, refer to Viewing Server Logs from the Administration Console.If no IDs are specified, this filter selects all message IDs.Example list: 20,50-100,300MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: MessageIds
Message Substring	Defines 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: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: MessageSubstring
Enabled Servers	Defines a list of servers whose messages can cause WebLogic Server to generate a trap.If no server is specified, no traps will be generated.MBean: weblogic.management. configuration. SNMPLogFilterMBeanAttribute: EnabledServers