Prev |  | Next

## Chapter 11. Serviceability and Diagnostics

Virgo supports two kinds of logging: Event Logging and Trace logging which is usually referred to simply as Logging. The difference between Event Logging and Logging is explained below, but both are configured in the `serviceability.xml` file in the `configuration` directory. This file takes the form of a Logback configuration, Virgo uses a Logback implementation behind the SLF4J logging interface.

For a description of the syntax and facilities provided by `serviceability.xml` see the Logback documentation (referenced in Appendix C. Further Reading ).

## Event Logging

Event logging records important events in Virgo. Each event is logged to an event log file and is accompanied by a code enclosed in angle brackets. An example is shown below:

    [2010-10-25 16:20:45.897] system-artifacts             <TC0010I> Creating HTTP/1.1 connector with scheme http on port 8080.

(For a description of the log code syntax, see Appendix A. Event log codes.) The format of event log messages is fully configurable.

By default, event log messages are stored in `$SERVER_HOME/serviceability/eventlogs/eventlog.log`.

The default behaviour is that, once `eventlog.log` reaches a 10Mb limit, it rolls into a series of files named `eventlog_`i`.log` where i ranges from 1 to 4, and event logging continues in a new `eventlog.log` file.

Prev |  | Next
| Home |