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 upHTTP 307 from alertmanager is not respected #1368
Comments
grobie
added
the
bug
label
Feb 4, 2016
This comment has been minimized.
This comment has been minimized.
|
Dupe of #668 |
brian-brazil
closed this
Feb 4, 2016
This comment has been minimized.
This comment has been minimized.
|
That said, this particular case can be fixed by sanitizing the appending of the API endpoint #1370. |
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.
lae commentedFeb 4, 2016
This occurs with alertmanager 1.0.0.beta1 and 2, and with alertmanager.url set to a url with a trailing slash (e.g.
/usr/bin/prometheus -alertmanager.url=http://localhost:9093/) in Prometheus:Prometheus doesn't attempt to POST the data again, so Alertmanager never sees the alerts. Prometheus should respect that response code and POST the data again (for this particular problem stripping out trailing slashes from alertmanager.url would be fine, but that's ugly).