Skip to content
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

Closed
imorph opened this issue Oct 14, 2024 · 6 comments · Fixed by #2226
Closed

[➕ Feature]: Manually execute workflows on incidents #2197

imorph opened this issue Oct 14, 2024 · 6 comments · Fixed by #2226
Assignees
Labels
Feature A new feature UI User interface related issues

Comments

@imorph
Copy link
Contributor

imorph commented Oct 14, 2024

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:

  • bunch of alerts generated and batched into incident (lets say by a "server" field)
  • user can create jira ticket about this incident by executing workflow
  • workflow have access to all alerts within incident, so all of them listed in ticket (richer context available)
  • incident have backlink to created ticket

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

@talboren
Copy link
Member

Hey @imorph! Thanks for opening this issue!

This is already possible and was implemented by @VladimirFilonov. Happy to elaborate further on our Slack: #1861

@talboren
Copy link
Member

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 🙏🏼

@imorph
Copy link
Contributor Author

imorph commented Oct 14, 2024

@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 15 incidents per day and only 5 of them are worthy creating ticket (execute "Create Ticket" workflow), for 6 of them there easy remediation exists (execute workflow "Easy Remediation") and rest 4 is not a problem so we can safely remove them.

@talboren
Copy link
Member

@imorph thanks for the clarification. This absolutely deserves a ticket then :) we’ll get to it ASAP.

@talboren talboren reopened this Oct 14, 2024
@talboren talboren changed the title [➕ Feature]: Execute workflows on incidents [➕ Feature]: Manually execute workflows on incidents Oct 14, 2024
@talboren talboren added Feature A new feature UI User interface related issues labels Oct 15, 2024
@VladimirFilonov
Copy link
Contributor

Hello @imorph! I just merged the possibility of manually running workflows for incidents, which will be available in the next release.

@imorph
Copy link
Contributor Author

imorph commented Oct 17, 2024

@VladimirFilonov WOW!

That speed of iteration is supper impressive! Thank you! Will check it next release and write back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature A new feature UI User interface related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants