Re: Haproxy monitoring with munin

On Wed, Mar 31, 2010 at 07:43:26AM -0700, Hank A. Paulson wrote:
> On 1/16/10 5:46 PM, Bart van der Schans wrote:
> >Hi,
> >
> >A few days ago there's was some interest in munin plugins for haproxy.
> >I have written a few plugins in perl. To code is fairly strait forward
> >and should be quite easy to adjust to your needs. The four attached
> >plugins are:
> >
> >- haproxy_check_duration: monitor the duration of the health checks per
> >server
> >- haproxy_errors: monitor the rate of 5xx response headers per backend
> >- haproxy_sessions: monitors the rate of (tcp) sessions per backend
> >- haproxy_volume: monitors the bps in and out per backend
> >
> >To use them you'll have to add something like the following to your
> >munin-node config:
> >
> >[haproxy*]
> >user haproxy
> >env.socket /var/run/haproxy.sock
> >
> >The user should have rights to read and write to the unix socket and
> >env.socket should point to the haproxy stats socket.
> >
> >For debugging the "dump" command line option can be quite useful. It
> >print the complete %hastats data structure containing all the info
> >read from the socket with "show stat". I can setup some
> >sourceforge/github thingie which will make it easier to share
> >patches/updates/additions/etc. if people are interested.
> >
> >Regards,
> >Bart
>
> I noticed the 1.4.4 version of Munin complains:
> Service 'haproxy_errors' exited with status 1/0.
>
> The normal (non-error) exit paths seem to require exit 0 not exit 1
 

Also, be careful when monitoring 5xx responses. 501 and 505 can be triggered by the client, so they are false positives.

Willy Received on 2010/04/01 07:20