-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve Execution Notifications plugins to allow passing custom payload #6457
Comments
Better to use the |
Agree with Loic, this one sounds like we need more info too. @wrussell1999 do you have the user name raising this need? I would like to have more details on the flow and corresponding trigger involved - reading the issue title "Improve Execution Notifications plugins to allow passing custom payload" it sounds like a broader subject around notification isn't? |
@Ben8t it's me :) |
Ah great :) Let's keep the discussion here as we have the proper issue! |
My setup: I get a Slack alert for all flows that end up with either FAILED or WARNED in the respective namespace. prod alerts go to the prod alert channel, dev alerts go to the dev alert channel. However, the error message is a bit crude at the moment, I only managed to include in the Slack message which flow, execution_id, and where the link is to access the logs. I would love to additionally display part of the error logs in the Slack message. I haven't yet managed to look more into the log.Fetch task, and if it would help me here. I thought that the new {{ errorLogs() }} pebble function could cover my needs, but it's not available via trigger. my slack alert task:
|
Thanks for the details, very clear now :) The good thing with the fetch.log task is that you can provide the |
It kind of works. adjusted workflow:
output of the get_error_logs task: |
Feature description
Add the ability to be able to get the
{{ errorLogs() }}
function inside of a Flow Trigger that runs when flows fail. This allows for instance wide error handling with useful errors inside of them.From a user in Slack:
The text was updated successfully, but these errors were encountered: