Replies: 1 comment
-
|
Should be doable. Could you please create an Feature Request issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Kibana v 8.19 webhook connectors require a fixed URL configuration per connector. This creates a limitation when integrating with devlake API webhook beacuse closing incident has dynamic path parameters like issueKey .
Kibana doen't support dynamically constructing the webhook URL using values from the alert context or previous action output.
As a result, it is not possible to reliably implement a “create + close” workflow using only Kibana alert actions when the external API requires the issueKey identifier in the URL path.
Proposed improvement
Workaround
At the moment, this limitation forces users to implement external middleware to store and correlate issueKey values between alert firing and recovery events.
Beta Was this translation helpful? Give feedback.
All reactions