...
Follow the instructions below to set up logging.1.
- Sign in. Enter your
...
- username and password to log on to the Management Console.
...
- Click
...
- Configure
...
- to access the
...
- Configure
...
- menu.
...
- From the
...
- Configure
...
- menu, select
...
- Logging.
...
...
The
...
Logging Configuration
...
window appears.
Info title Tip If you select the "Persist All Configurations Changes" check-box, all modifications will be persisted, and they will be available even after a server restart.
...
- The
...
- Logging Configuration
...
- window has three sections:
Using these sections, you can configure the layout and the amount of information about system activity you want to receive.
| Anchor | ||||
|---|---|---|---|---|
|
This section allows you to assign a single log level and log pattern to all loggers.
- Log Level - Reflects the minimum level that this logger is concerned with. You can view the hierarchy of levels #below below.
- Log Pattern - Defines the output format of the log file.
| Anchor | ||||
|---|---|---|---|---|
|
This section allows you to configure appenders. Log4j allows logging requests to print to multiple destinations. These output destinations are called "Appenders." You can attach several appenders to one logger.
...
- TRACE - Designates finer-grained informational events than DEBUG.
- DEBUG - Designates fine-grained informational events that are most useful to debug an application.
- INFO - Designates informational messages that highlight the progress of the application at a coarse-grained level.
- WARN - Designates potentially harmful situations.
- ERROR - Designates error events that might still allow the application to continue running.
- FATAL - Designates very severe error events that will presumably cause the application to abort.
| Anchor | ||||
|---|---|---|---|---|
|
This section allows you to browse through all loggers, define a log level, and switch on/off additivity to any of them.
...