edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Filter log messages

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Filter log messages

Before you begin


Configuring a filter lets you specify criteria for accepting log messages for publishing; only the log messages that satisfy the filter criteria get published. You can filter log messages going to the log file, standard output, the domain log, or the memory buffer.

Setting a severity level is the simplest type of log message filtering; for example, any message of a lower severity than the specified threshold severity level, will be rejected. For example, by default, the Stdout Handler has a NOTICE threshold severity level. Therefore, INFO and DEBUG level messages are not sent to standard out. You can also use the Logger severity properties box to specify severity levels for individual Loggers (if using the Message Catalog Logger) or packages (if using the Commons Logging API).

To filter log messages by severity level or other criteria:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, expand Environment and select Servers.
  3. Under Servers, click the name of the server instance whose logging you want to configure.
  4. On the Logging: General page, click Advanced.
  5. From the Logging implementation list box, select the logging implementation you are using. For more information, see How to Use Log4j with WebLogic Logging Services.
  6. In the Minimum severity to log list box, specify the minimum severity level for the root Logger. This is used as the default severity level for all loggers or packages in the logger tree. For information about message severity, see Message Severity.
  7. Select the Redirect stadout logging enabled option if you want to redirect the standard out of the JVM in which the WebLogic Server instance runs to the four log message destinations (log file, standard out, domain log, and message buffer). For more information, see Redirecting JVM Output.
  8. In the Logger severity properties box, specify the severity level for any loggers for which you want to override the setting for the root Logger (as specified by the Minimum severity to log list box) or its closest parent node in the logger tree. You can also use Logger severity properties to specify severity levels for packages (if using the Commons Logging API) or for individual WebLogic Server subsystem Loggers (if using the Message Catalog Logger). For more information, see Specifying Severity Level for Loggers.
  9. Under the Message destination(s) section, specify filtering for messages going to each of the four log message destinations (Log file, standard out, domain log broadcaster, and memory buffer):
    1. Select a severity level in the Severity Level list box.

      Only messages of the selected severity or higher are forwarded to the destination. For information about message severity, see Message Severity. Note that you cannot forward DEBUG messages to the domain log.

    2. In the Filter list box, select a filter to qualify log events being sent to the destination.

      For more information, see Create log filters.

  10. Under the Message destination(s):Domain log broadcaster section, specify the size of the message buffer which stores messages that will be forwarded to the domain log. A higher value causes more messages to be stored in the buffer before the contents are forwarded to the domain log. For performance reasons, It is recommended that this value be set to 10 or higher in production mode.
  11. Click Save.
  12. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result

Only messages that satisfy the qualifying criteria will be published to the log message destination.


Back to Top