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

Create a counter/gauge metric that exposes scrape errors #1

Closed
marcelcorso opened this issue Mar 31, 2017 · 4 comments
Closed

Create a counter/gauge metric that exposes scrape errors #1

marcelcorso opened this issue Mar 31, 2017 · 4 comments

Comments

@marcelcorso
Copy link
Contributor

Right now it's not easy to monitor if clickhouse_exporter can reach it's target.

For example: To solve that problem Prometheus' jmx_exporter exposes a gauge:

# HELP jmx_scrape_error Non-zero if this scrape failed.
# TYPE jmx_scrape_error gauge
jmx_scrape_error 0.0

that goes to 1 when there is a problem scraping it's target.

It would be great to have something like this for clickhouse_exporter.

@f1yegor
Copy link
Contributor

f1yegor commented Apr 1, 2017

Will look at this

@f1yegor
Copy link
Contributor

f1yegor commented Apr 19, 2017

it's already exposed exporter_scrape_failures_total
in grafana you can use sum(exporter_scrape_failures_total) OR vector(0)

PS. if you are using grafana you can also look at https://grafana.com/dashboards/882

@marcelcorso
Copy link
Contributor Author

We are using the grafana dashboard 👍 . But because we have many clickhouse instances its getting a bit busy. But that's another problem :-)

I saw the exporter_scrape_failures_total but I'm not sure how to alert on it.

If the rate(exporter_scrape_failures_total[1m]) > 0 sounds weird

@f1yegor
Copy link
Contributor

f1yegor commented Apr 28, 2017

Looks legit. If you have further questions feel free to reopen an issue.

@f1yegor f1yegor closed this as completed Apr 28, 2017
vfoucault pushed a commit to vfoucault/clickhouse_exporter that referenced this issue Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants