-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Http connections not being closed #31
Comments
this is what I'm struggling as well. Any workaround? |
@jjuraszek We had to resort to a cron job that restarted our exporter every couple of hours so that we could force close the connections. |
This open PR #39 seems to fix the problem. |
Now that #39 is merged, can this issue be closed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're running prometheus-to-cloudwatch in a kubernetes pod to scrape our selenium endpoint for metrics. This is working but after a couple of hours it causes the selenium exporter to become unavailable as the http connections are being held open so no new ones can be created. We're having to restart the exporter to get everything working again. Is there a way to get prometheus-to-cloudwatch to close the http connections after it has made them so that it isn't leaving them hanging?
The text was updated successfully, but these errors were encountered: