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

nginx_up metric name is misleading #978

Open
grepwood opened this issue Feb 13, 2025 · 2 comments
Open

nginx_up metric name is misleading #978

grepwood opened this issue Feb 13, 2025 · 2 comments
Labels
enhancement Pull requests for new features/feature enhancements help wanted Issues identified as good community contribution opportunities proposal An issue that proposes a feature request refined Issues that are ready to be prioritized

Comments

@grepwood
Copy link

Describe the bug
nginx_up's name implies that it indicates whether nginx is up or not - not that the scrape was successful, as the documentation for nginx-prometheus-exporter states. As such, this creates an opportunity to confuse users by giving them false negatives - they will believe that nginx is down based on nginx_up returning 0 - when in reality, nginx returned a perfectly normal HTTP error, which it could have not done if it wasn't up.

To reproduce
Steps to reproduce the behavior:

  1. Deploy any version of nginx and configure it deliberately to serve any HTTP error for GET /stub_status.
  2. Deploy nginx-prometheus-exporter and tell it to scrape metrics from that nginx from the usual place.

Expected behavior
If nginx_up's definition were consistent with its name, it would return true. The status of whether a scrape has succeeded, should be described in a different metric.

Your environment

  • Version of the Prometheus exporter - 1.4.1
  • Version of Docker/Kubernetes - not relevant
  • [if applicable] Kubernetes platform (e.g. Mini-kube or GCP) - not relevant
  • Using NGINX or NGINX Plus - NGINX 1.26.2
@jjngx jjngx added needs triage bug An issue reporting a potential bug labels Feb 27, 2025
@vepatel vepatel added proposal An issue that proposes a feature request and removed bug An issue reporting a potential bug needs triage labels Mar 6, 2025
@sindhushiv
Copy link

@shaun-nx @mpstefan Can you please take a look at it?

@mpstefan
Copy link

This makes sense, and very welcome to take any PRs on this issue.

@mpstefan mpstefan added enhancement Pull requests for new features/feature enhancements help wanted Issues identified as good community contribution opportunities refined Issues that are ready to be prioritized labels Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Pull requests for new features/feature enhancements help wanted Issues identified as good community contribution opportunities proposal An issue that proposes a feature request refined Issues that are ready to be prioritized
Projects
None yet
Development

No branches or pull requests

6 participants