Administration Console Online Help
Tasks Related Topics Attributes
The Domain Log FilterERROR
or higher are sent.
Note: HTTP requests, JDBC messages, JTA transactions, and messages of severity DEBUG
are never sent to the domain log, even if you use a filter.
If you are creating a new filter, you must enter information on the Configuration tab and click Apply before you can access other tabs. Once you create a filter, you cannot change its name. Instead, you must create a new filter under a different name.
After you create a filter, you activate it by targeting it to one or more servers.
Specifying the Messages That a Server Forwards to the Domain Log
Specifying Which Messages a Server Sends to Standard Out
Local Log Files and Domain Log Files
An alpha-numeric value that identifies the filter. This name attribute is for your identification purposes only. After you have created a domain log filter, you cannot change its name. Instead, clone the filtter and provide a new name for the clone. For more information, refer to Cloning a Domain Log Filter. MBean: |
||
The minimum severity of a message that this filter forwards to the domain log. All messages with the specified severity and higher will be sent to the domain log. The ascending order of severities is as follows:
MBean: |
||
The user IDs for which associated messages are sent to the domain log. If no IDs are specified, messages from all user IDs can be sent to the domain log. Every message includes the user ID under which the associated event was executed. To execute some pieces of internal code, WebLogic Server authenticates the ID of the user who initiates the execution and then runs the code under a special Kernel Identity user ID. J2EE modules such as EJBs that are deployed onto a server instance report the user ID that the module passes to the server. MBean: |
||
A list of subsystems whose messages are selected by this log filter. If none are specified, messages from all subsystems are selected. MBean: |