Finding out number of healthy backends

[Glen Kelly]

A decision was made not to run the console, one less avenue for an attack. The servers are protected behind firewalls but it was thought there would be one less potential vulnerability.

Is there any other way of finding the number of healthy backends?

Regards Glen

From: Guido Bakker [mailto:guido.bakker at gmail.com]
Sent: Tuesday, 23 November 2010 5:33 PM
To: Glen Kelly
Cc: varnish-misc at varnish-cache.org
Subject: Re: Finding out number of healthy backends

We build a nagios check using:

varnishadm -T localhost:6082 debug.health | grep \ is

This works fine.
2010/11/22 Glen Kelly <Glen.Kelly at fire.tas.gov.au<mailto:Glen.Kelly at fire.tas.gov.au>>
Is there any way of using varnishstat to determine the number of healthy backends?

I currently use 'varnishstat -1 -f n_backend' but this only returns the number of backends, not the number of healthy backends.

I am using Nagios to monitor our environment and want to be able to monitor when we lose a backend. I already am monitoring the backends directly so I have that covered but I want to also monitor when varnish thinks it has lost a backend. i.e. monitoring at multiple levels

If this is not current achievable how do I go about requesting this feature to be added to varnish?

Regards Glen

Error! Filename not specified.<http://www.fire.tas.gov.au/Show?pageId=colDayLightSavings>

P Do you need to print this? Consider the environment, prevent paper waste.

CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.



_______________________________________________
varnish-misc mailing list
varnish-misc at varnish-cache.org<mailto:varnish-misc at varnish-cache.org>
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20101124/44adfb84/attachment-0003.html>