-
Notifications
You must be signed in to change notification settings - Fork 458
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
Howto get upstreams state #262
Comments
@adrimt Thanks reporting! |
I change the config to define an "upstream" but it didn't behave differently. upstream web01-http { server { |
@adrimt nginx-module-vts/share/status.template.html Line 685 in 5b3812e
Moreover nginx oss doesn't change peer->down anywhere below.
We should match the behavior due to display mode both |
@adrimt
Thus, we could not fix the view point of peer->fails with peers->single by any nginx upstream patch.
So we should embed other request based module to collect such stats, e.g. we can use nginx_upstream_check_module on workaround. compile with pure nginx
nginx.conf
The upstream peer is up |
Thank you for clarifying this issue. |
Hi,
the upstream state is always 'UP' even when the backend serer is down and the nginx return code is 502.
Did I miss something ?
vhost_traffic_status_zone;
geoip_country /usr/share/GeoIP/GeoIP.dat;
vhost_traffic_status_filter_by_set_key $geoip_country_code country::*;
vhost_traffic_status_zone shared:vhost_traffic_status:32m;
server {
listen 10.10.10.1:80;
server_name $hostname;
location /status {
vhost_traffic_status_display;
vhost_traffic_status_display_format html;
access_log off;
}
}
server {
listen 10.10.10.10:80;
server_name webserver1;
location / {
proxy_pass http://192.168.10.10;
...
}
}
The text was updated successfully, but these errors were encountered: