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 upConfig reload via HTTP API should return status code #1425
Comments
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
Related to #1149 |
brian-brazil
added
the
feature-request
label
Feb 24, 2016
brian-brazil
referenced this issue
Feb 29, 2016
Closed
Failed reloads are not exposed through web API #1292
This comment has been minimized.
This comment has been minimized.
|
Per #1292, having the error message would be good too. |
fabxc
added
kind/enhancement
and removed
feature request
labels
Apr 28, 2016
pydima
referenced this issue
Jul 11, 2016
Merged
web: return status code and error message for config resource #1804
fabxc
closed this
in
#1804
Jul 15, 2016
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. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
RichiH commentedFeb 24, 2016
As of right now,
prometheus_config_last_reload_success_timestamp_secondsprovides information from within Prometheus on if a reload was successful or not, but a simple return to the caller would allow me to see if everything was fine from CLI.