...
| Table of Contents | ||||
|---|---|---|---|---|
|
Logging Configuration
At this state the configurability of logging stage configuration will be limited to selection of logging level. Further details on the approach to provide configurable logging can be found hereto the addtion to the main config.xml file of the following option:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<broker>
...
<logging>
<level>INFO</level>
<logging>
</broker>
|
This INFO level setting will be the default value if the section is not included in the configuration file. The setting will be global for all virtualhosts and will be exposed via the management console as logger 'qpid.operational' to allow dynamic level setting.
The ability to configure more fine grained logging will be investigated here, but will not be implemented in the initial phase.
Logging Levels
The following six levels represent the range of levels that will be available as part of the logging configuration. Whilst the initial implementation may not include specific messages at each level this section simply describes the type of message that would appear at each level and the behaviour associated with logging at that level. The levels are listed in order of the frequency of logging events. In addition to these six levels the values ALL and OFF may be used, these respectively represent TRACE and FATAL. FATAL messages will always be logged as they are associated with a broker shutdown.
...
The LogEntity allows the OperationLogger to delegate the creation of the formated prefix as specfiecied here. Further additions to this interface may be required to enable selective configurations however this is not part of this design.
The addition of the ability to set a creator allows for situations such as Binding to have a Connection associated with the Binding. This will allow a Binding create event to be logged like this:
| No Format |
|---|
2009-06-29 13:35:10,1234 +0100 INFO [ con:1(guest@127.0.0.1/)/ch:2/ex(amq.direct)/qu(testQueue)/bd(routingKey) ] Created Binding
|
rather having no details about how the creation occured:
| No Format |
|---|
2009-06-29 13:35:10,1234 +0100 INFO [ vh(/)/ex(amq.direct)/qu(testQueue)/bd(routingKey) ] Created Binding
|
Logging Usage
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
pubic class Subscription
...
if (_statusLogger.isInfoEnabled(this))
{
_statusLogger.info(this, "Subscription Event occured.");
}
...
|
...
| No Format |
|---|
2009-06-29 13:35:10,1234 +0100 INFO [ con:1(guest, 127.0.0.1, /)/ch:2/sub:1:qu(myqueue) ] Subscription Event occcured.
|
...
| No Format |
|---|
2009-06-29 13:35:10,1234 +0100 INFO [ con:1(guest, 127.0.0.1, /)/ch:2/pl(ACL, Consume, qu(myQueue)) ] Plugin Event occured for this.
|
...