-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
alert_text doesn't work when sending alert to a POST server #2083
Comments
This is a bug (or feature 😉 ). You can't add it easily right now, but this is definitely something I want to fix. There's some workarounds you could do. One is to create an enhancement that would create this string so you can put it into the http_post_payload. This would require writing a small amount of Python code though. If you want some help on that let me know. |
Ok, Thanks for caring about it. |
I had the same problem,and i want to know when to fix it, thanks~~ @Qmando |
Hi @Qmando |
Hello.
I've this rule:
Alerts are received by post server correctly (in fact, this server is public, so you can see the content of the received message if you go to http://ptsv2.com/t/lalala) BUT alert_text+alert_text_type+alert_text_args options are completely ignored: received message on server is a JSON which, moreover, I can't relate to theorical default alert's body explained here https://elastalert.readthedocs.io/en/latest/ruletypes.html#alert-content
Do you know why? Am I doing something wrong? Is it a bug?
Thanks!!!
The text was updated successfully, but these errors were encountered: