-
Notifications
You must be signed in to change notification settings - Fork 14
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
Response time for /mertics is more than 2mins #69
Comments
This probably means it can't connect to chrony properly. |
Thanks for the quick response, enabled debug logs, below are the same for one request, took more than 2mins, why is it making multiple requests internally? ts=2024-03-13T19:40:15.191Z caller=sources.go:100 level=debug msg="Got 'sources' response" sources_packet=SUCCESS |
I think you are seeing multiple scrape requests interleaved. As for slowness, my first guess is DNS lookups for you are very slow. Try |
Give v0.9.1 a try. |
@SuperQ , Thank you so much for the superfast patch release. Sorry for the delay, bit occupied. ts=2024-03-17T10:44:46.618Z caller=collector.go:147 level=debug scrape_id=413 msg="Scrape starting" |
Looks like you have a broken server somewhere. I would recommend using CoreDNS. It can provide local caching. Either way, this doesn't look like an exporter issue. |
Thanks for the recommendation. Yes, either way it is not exporter issue. |
Noticed chrony_exporter taking more than 2mins to respond with metrics.
Versions Tried: 0.9.0 and 0.8.0
Environment: x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: