load balancer on nginx : how to monitoring backend ?

CJ Ess zxcvbn4038 at gmail.com
Fri Jan 29 04:54:25 UTC 2016


Does anyone know if the author still maintains nginx_upstream_check_module?
I see only a handful of commits in the past year and they all look like
contributed changes.

On Thu, Jan 28, 2016 at 9:28 PM, Dewangga Bachrul Alam <
dewanggaba at xtremenitro.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hello!
>
> If you are in development, you can try this module
> https://github.com/yaoweibin/nginx_upstream_check_module. But, not
> recommended if use on production, better use n+.
>
> On 01/28/2016 02:36 PM, Alexandre wrote:
> > Hello,
> >
> > On 28/01/16 08:27, Maxim Konovalov wrote:
> >> On 1/28/16 1:32 AM, Alexandre wrote:
> >>> Monitoring of backend seems to be possible with NGINX PLUS. Can
> >>> you confirm ?
> >>>
> >>> http://nginx.org/en/docs/http/ngx_http_upstream_module.html
> >>> https://www.nginx.com/products/
> >>>
> >> Yes, that's right.
> >
> > OK, I can not use a load balancer in production without backend
> > monitoring. I will use LVS.
> >
> > Thank you.
> >
> > Alexandre.
> >
> >>
> >>> Thank you
> >>>
> >>> Alexande.
> >>>
> >>> On 27/01/16 22:37, Alexandre wrote:
> >>>> Hello, thank you I'll test.
> >>>>
> >>>> It is not possible to test the nginx upstream directly ?
> >>>>
> >>>> Thank you
> >>>>
> >>>> Alexandre
> >>>>
> >>>>
> >>>> On 27/01/16 20:40, Yichun Zhang (agentzh) wrote:
> >>>>> Hello!
> >>>>>
> >>>>> On Wed, Jan 27, 2016 at 9:10 AM, Alexandre wrote:
> >>>>>>
> >>>>>> However I wish to monitor the status of the backend. How
> >>>>>> can I do ?
> >>>>>>
> >>>>>
> >>>>> You may find the lua-resty-upstream-healthcheck library
> >>>>> helpful:
> >>>>>
> >>>>> https://github.com/openresty/lua-resty-upstream-healthcheck
> >>>>>
> >>>>>
> >>>>>
> But it's much easier to install via the OpenResty bundle though:
> >>>>>
> >>>>> https://openresty.org/
> >>>>>
> >>>>> Regards, -agentzh
> >>>>>
> >>>>> _______________________________________________ nginx
> >>>>> mailing list nginx at nginx.org
> >>>>> http://mailman.nginx.org/mailman/listinfo/nginx
> >>>>>
> >>>>
> >>>> _______________________________________________ nginx mailing
> >>>> list nginx at nginx.org
> >>>> http://mailman.nginx.org/mailman/listinfo/nginx
> >>>
> >>> _______________________________________________ nginx mailing
> >>> list nginx at nginx.org
> >>> http://mailman.nginx.org/mailman/listinfo/nginx
> >>>
> >>
> >>
> >
> > _______________________________________________ nginx mailing list
> > nginx at nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWqs5DAAoJEOV/0iCgKM1wIAcP/inWjW0CGSQ1R0zDkwi+j5Ac
> m3LVzIS86/Ft86BuJXcam3SC5Cf+1bCYM0rUsYx5xsTZMjnJhOOkLaPFSGJ4jwth
> E3Lu5qDckCttOdmndmWXPUWHdTLASJXjntLEQgY969h48ucJRoCmA3ZB9DsPql7e
> nJS4Rkcu9DV4bSiCB6gFMNUksI9em/G6N/P2kXkEl33I9wEi79O7y5sT16dXiGm0
> vTp5qozO2UtGtO6lfx3s0xYxUpsSiLYtYlfAY6335cuh1yFQqhMyNr2EgphtlY+1
> cMMQnlM8Sfut0YltRcV3YSq1d8je4QEXSK0mC8sSXJUE58V/C6otu/O1I/h1BnQO
> g0TKFDTQk1rN1/z3b9jirlObwdNbWmIq7hI9Nuwi3WilDB57iEoD+pmC7R2obKDS
> ItrkkAKWWTsDyQOH2BMCK4nqW+whHC7D3lFCrKuzsITJDrFJf6fjzlXRzniwH/1L
> VJgKaIlnX7M54zJwITZcDcYGmLuC/MRHNU9HK3QYDgwdPdgSccDQwlhBnxI7tNtS
> gSaEVpf9Af/8QIPPyLngvl6uGskvfQdXiWHmRb0SyTwZcJEDrutf6q//hwT59Mn4
> ZFLS7htPV8wCKvgxlFV7DtxRcbm9HBDRdt1ScrbTKQbLAxxQhpOVCV1emhFjfgem
> 020FGHFbMMmngyi50b1p
> =XA04
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160128/e1c91ac9/attachment.html>


More information about the nginx mailing list