You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Raphael Fuchs <ra...@gmail.com> on 2015/03/18 11:45:12 UTC
Monitoring Qpid Logs
Hello everyone,
I am using the qpid message broker. I need to setup an automatic monitoring
of the qpidd logs. The problem is: the daemon has been running so smoothly
in the past year, that I don't know which error messages to check for in
the logs.
If I enable (--log-enable warning+) is there a way to get a list of the
most important log messages in case of a problem?
Thank you!
Best regards
Raphael
Re: Monitoring Qpid Logs
Posted by Raphael Fuchs <ra...@gmail.com>.
Hi Chuck,
thank you!
Cheers,
Raphael
2015-03-23 14:45 GMT+01:00 Chuck Rolke <cr...@redhat.com>:
>
>
> ----- Original Message -----
> > From: "Raphael Fuchs" <ra...@gmail.com>
> > To: users@qpid.apache.org
> > Sent: Wednesday, March 18, 2015 6:45:12 AM
> > Subject: Monitoring Qpid Logs
> >
> > Hello everyone,
> >
> > I am using the qpid message broker. I need to setup an automatic
> monitoring
> > of the qpidd logs. The problem is: the daemon has been running so
> smoothly
> > in the past year, that I don't know which error messages to check for in
> > the logs.
> >
> > If I enable (--log-enable warning+) is there a way to get a list of the
> > most important log messages in case of a problem?
> >
> > Thank you!
> >
> > Best regards
> > Raphael
> >
>
> The most important log messages are arranged by log level:
>
> /** Debugging severity levels
> * - trace: High-volume debugging messages.
> * - debug: Debugging messages.
> * - info: Informational messages.
> * - notice: Normal but significant condition.
> * - warning: Warn of a possible problem.
> * - error: A definite error has occured.
> * - critical: System in danger of severe failure.
> */
>
> Within each level there is no relative ranking between log messages.
> That is, one warning is not more important than another warning.
>
> A useful high level view may be to count messages in a grid with
> the level on one axis and the category on the other.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Monitoring Qpid Logs
Posted by Chuck Rolke <cr...@redhat.com>.
----- Original Message -----
> From: "Raphael Fuchs" <ra...@gmail.com>
> To: users@qpid.apache.org
> Sent: Wednesday, March 18, 2015 6:45:12 AM
> Subject: Monitoring Qpid Logs
>
> Hello everyone,
>
> I am using the qpid message broker. I need to setup an automatic monitoring
> of the qpidd logs. The problem is: the daemon has been running so smoothly
> in the past year, that I don't know which error messages to check for in
> the logs.
>
> If I enable (--log-enable warning+) is there a way to get a list of the
> most important log messages in case of a problem?
>
> Thank you!
>
> Best regards
> Raphael
>
The most important log messages are arranged by log level:
/** Debugging severity levels
* - trace: High-volume debugging messages.
* - debug: Debugging messages.
* - info: Informational messages.
* - notice: Normal but significant condition.
* - warning: Warn of a possible problem.
* - error: A definite error has occured.
* - critical: System in danger of severe failure.
*/
Within each level there is no relative ranking between log messages.
That is, one warning is not more important than another warning.
A useful high level view may be to count messages in a grid with
the level on one axis and the category on the other.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org