-
Notifications
You must be signed in to change notification settings - Fork 57
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
Exporter suddenly fails to show any metrics. #86
Comments
As additional data: druid-exporter host is near 0% CPU usage and 0% RAM usage all the time, monitored with prometheus and htop while querying /metrics and it's a dedicated host so that's not the issue either :( |
Downloaded v0.8 of the exporter, the issue stops happening. Looks like there is something with v0.9 |
Ignore this issue. Apparently the host invoked the oom-killer, druid-exporter was the target and for reasons I cannot see the service we created (that just runs druid-exporter) is not working. Doesn't matter which version run. If I run the exporter myself (or with any other user) it works. Time to investigate this on my own. Sorry for bothering you! :) |
Sorry for all the back and forth. Apparently yes, it only happens in v0.9 released. v0.9-beta works OK |
I'll check this over the weekend |
Fixed in #89 |
Fixed in v0.9 release https://github.com/opstree/druid-exporter/releases/tag/v0.9 |
The release one was the affected by this issue. How is it fixed on that one? 🤔 |
Ok, I've got myself an X Files case here.
Our druid-exporter suddenly died yesterday around 20:00 (CET).
This are the logs:
Since then, we've got 0 metrics. Tried reinstalling, rebooting the instance, restarting the router, broker, overlord, coordinator... 0 metrics.
Logs are empty, besides the typical "starting 8080, endpoint X, endpoint Y"
A tcpdump shows that the instance is receiving metrics from druid.
curl-ing the metrics in druid-exporter returns metrics, but takes ages, just now I timed it:
Any idea what might have happened?
The text was updated successfully, but these errors were encountered: