-
Notifications
You must be signed in to change notification settings - Fork 806
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
[➕ Feature]: Manually execute workflows on incidents #2197
Comments
Hey @imorph! Thanks for opening this issue! This is already possible and was implemented by @VladimirFilonov. Happy to elaborate further on our Slack: #1861 |
I'm going to go ahead and close this issue, but if you feel like there's still place for this issue to exist, please re-open it 🙏🏼 |
@talboren thanks for quick reply! As I understand that change, it is more about adding incident lifecycle events (create/update/delete) as automatic triggers for workflow execution. That is great addition, but I am talking about more manual (or user involving) use case when "operator" have lets say |
@imorph thanks for the clarification. This absolutely deserves a ticket then :) we’ll get to it ASAP. |
Hello @imorph! I just merged the possibility of manually running workflows for incidents, which will be available in the next release. |
@VladimirFilonov WOW! That speed of iteration is supper impressive! Thank you! Will check it next release and write back |
Problem statement
It is cool that we are able to get bunch of different alerts to be correlated and batched into single incident automatically. But it will be even more useful if it would be possible to execute workflow on this incident.
Exact user story may looks like this:
Basically it is how it works right now with individual alerts but on incident level. For now if something happens with "server" we got separate alerts for "cpu", "disk", "network" etc and for each of them individually it is possible to create tickets but essentially this is single "Incident" and to have one jira ticket per one incident is great.
But may be I am missing something and this is already possible (we use 0.24.5)?
Thanks
The text was updated successfully, but these errors were encountered: