[Alerting] creating alert with slack action with bad action variable results in 400 response on execution #60042
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v7.7.0
Create a slack action pointing to a real slack webhook. Create an index threshold alert that will actually fire, and add the slack action to it. For the "message" parameter, enter
{{{message}}}
.Once the slack action fires, you should see a 400 response from slack in the Kibana log:
Change the "message" parameter value to
{{{context.message}}}
and save, and the messages will start working.Not sure what's going on there, but the
{{{message}}}
is clearly incorrect, as we don't have a variable with that name. Does it end up rendering as an empty string, and so Slack ignores it?If that's it, then we should fix this for 7.7, because I'm sure people will end up hitting this.
Seems like we may want to have some check to see if required parameter values are non-empty, within the actions. Maybe that's where it's coming from in this case, but then the message isn't very clear about the problem.
We could perhaps default "empty" required values to a value which indicates the param was "empty" - in this case something like
slack message was an empty string in action parameters
The text was updated successfully, but these errors were encountered: