-
Notifications
You must be signed in to change notification settings - Fork 495
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
Chained notifications have empty body #2304
Comments
Hi @rickynils, apologies for the late response. I didn't manage to reproduce the bug with the minimal config below and the latest code from master.
This config produced the expected output:
Do you have any further instructions on how to reproduce the issue? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(this issue might be related to #2226 and/or #1583 (comment))
I have alerts with chained notifications that look like this (you can probably completely ignore the mail notifications here, they work fine. It's the HTTP POST notifications that don't work correctly):
I have a low timeout (
1m
) for debug purposes. Longer timeouts behave the same.When a critical alert is triggered, the first notifications (
phone1
andmail1
works as expected. However, if don't acknowledge the alert, and let go on to the next notification (phone2
), the HTTP POST request is performed with an empty body (size 0).Look at the logs below:
Look at the two last lines. Bosun correctly picked the
body2
field, but it never set it toBODY2
as expected, instead it just POSTed an empty body, causing a 400 bad request for the HTTP endpoint.The text was updated successfully, but these errors were encountered: