-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix/prometheusexporter Shutdown HTTP server #35465
Fix/prometheusexporter Shutdown HTTP server #35465
Conversation
00e689f
to
52eee00
Compare
Hey @Aneurysm9, @songy23, sorry for pinging you directly. Do you mind having a look at this or advising me what is needed from me to go ahead with this PR? |
1c1ef8f
to
6efa063
Compare
unit tests seem to fail after the change. |
Yeah, I just took a look at the teste that are failing, and I'm not sure what's happening there:
Is this a workaround for the fact that the server did not shutdown correctly previously, and is now failing, because after the shutdown the server is shutdown? |
It might have been. Try removing the httpClient.Get call from cleanup and see if tests pass. |
These statements seem to be a workaround for the server not being closed correctly, with the previous changes this should no longer be necessary
381f74f
to
7b7535f
Compare
After removing the statements the tests passed locally for me. Sorry for not running them in the first place, I had some troubles running them using make... :/ |
Is there something you need me to do? |
**Description:** Shutdown the http.Server instance on exporter shutdown **Link to tracking Issue:** open-telemetry#35464 **Testing:** Manual testing. I included this version of the exporter in our internal distribution and deployed it to verify the metrics no longer go stale after receiving a `NOHUP` signal. **Documentation:** n/a --------- Co-authored-by: David Ashpole <dashpole@google.com>
**Description:** Shutdown the http.Server instance on exporter shutdown **Link to tracking Issue:** open-telemetry#35464 **Testing:** Manual testing. I included this version of the exporter in our internal distribution and deployed it to verify the metrics no longer go stale after receiving a `NOHUP` signal. **Documentation:** n/a --------- Co-authored-by: David Ashpole <dashpole@google.com>
Description: Shutdown the http.Server instance on exporter shutdown
Link to tracking Issue: #35464
Testing: Manual testing. I included this version of the exporter in our internal distribution and deployed it to verify the metrics no longer go stale after receiving a
NOHUP
signal.Documentation: n/a