Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VTS Upstream groups not working with --enable-dynamic-configuration #2355

Closed
valeriano-manassero opened this issue Apr 16, 2018 · 8 comments · Fixed by #2608
Closed

VTS Upstream groups not working with --enable-dynamic-configuration #2355

valeriano-manassero opened this issue Apr 16, 2018 · 8 comments · Fixed by #2608

Comments

@valeriano-manassero
Copy link

Using --enable-dynamic-configuration causes Nginx Vhost Traffic Status on /nginx_status to show only one upstream group:

upstream_balancer

This group metrics are never updated too.
This is due of LUA taking care of load balancing of the only upstream group declared in nginx.conf.
But this behavior completely eliminates any backend metric.

I already tried to workaround this but without luck. Have you any ideas on how to tackle this?

@aledbf
Copy link
Member

aledbf commented Apr 16, 2018

This group metrics are never updated too.

We are aware of this limitation

I already tried to workaround this but without luck. Have you any ideas on how to tackle this?

Not yet. I think we need to start porting some features like this one and Prometheus to LUA land using a custom module using go as the backend of the module to avoid the limitations of LUA dictionaries for this kind of tasks

@aledbf
Copy link
Member

aledbf commented Apr 16, 2018

@ElvinEfendi ping

@ElvinEfendi
Copy link
Member

We have started looking into this in the context of monitoring ingress-nginx in general. My colleague @fmejia97 is working on this. The idea is first to document the existing monitoring options, then document what's desired and what's missing and then implement the missing ones.

@mikksoone
Copy link

Any update on this? Is the plan to fake it for VTS or use custom monitoring solution that provides similar data via prometheus etc?

@ElvinEfendi
Copy link
Member

@mikksoone we are expecting to have something by the end of this month. The plan is to implement something similar to what VTS provides in Lua.

@valeriano-manassero
Copy link
Author

There are some progress on this?
Thank you.

@aledbf
Copy link
Member

aledbf commented Jun 6, 2018

@valeriano-manassero yes, please check #2608

@aledbf
Copy link
Member

aledbf commented Jun 14, 2018

@valeriano-manassero just in case, please don't use this change yet, we need to clean up some things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants