Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow reloading via webhandler #923
Comments
This comment has been minimized.
This comment has been minimized.
|
We already have a feature to quit Prometheus remotely (optionally enablable by setting the So unless we want to also remove that (I don't think anyone actually uses it), it could make sense to also add a reload endpoint. You'd probably just need to pass this channel to the web handler and make the handler send signals over it when called: prometheus/cmd/prometheus/main.go Line 104 in 276dbf8 |
This comment has been minimized.
This comment has been minimized.
|
I have actually used the quithandler because sometimes we get phantom jobs, but maybe that just means I'm the only one. Your suggested solution is more elegant than mine was -- I just had the web handler send SIGHUP to itself. The channel is a better idea :) |
This comment has been minimized.
This comment has been minimized.
|
This was implemented in #976 |
juliusv
closed this
Sep 14, 2015
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
swsnider commentedJul 22, 2015
Right now, config can only be reloaded by sending SIGHUP to prometheus's process. It would be significantly easier for the automation that I'm writing to distribute our configuration to our prometheus instances if we were able to do the equivalent from a POST to the prometheus http server.
Is this something that you've already decided was a bad idea? I notice that in #108, you decided against file watches for different reasons than would seem to apply here.