eG Monitoring
 

Measures reported by QpidBrokrLogTest

Loggers are responsible for writing of a log. The log includes log events that match a Logger's inclusion rules. Loggers are associated with either the Broker or a virtual host. Virtual host loggers write only log events related to that virtual host. Broker Loggers write log events from the Broker as a whole. Optionally a Broker Logger can be configured to exclude log events coming from virtual hosts. These abilities can be usefully exploited together in managed service scenarios to produce separate logs for separate user groups. Loggers can be added or removed at runtime, without restarting the Broker. However changes to a Logger's configuration such as file names and rolling options don't take effect until the next restart. Changes to a Logger's inclusion rules take effect immediately. This test reports the current state of the broker log files and alerts the administrators for any errors/warnings that exist in the broker log files.

Outputs of the test: One set of results for the target Apache Qpid Java Broker.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
state Indicates the current state of the Broker log file.  

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Stopped 0
Quiesced 50
Uninitialized 60
Unavailable 70
Errored 80
Deleted 90
Active 100

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of the Broker log file.

errorCount It indicates the number of errors in the Broker log file. Counts

A very low value is desired for these measures.

warnCount It indicates the number of warnings in the Broker log file. Counts

A very low value is desired for these measures.