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.

Sign up for GitHub

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

Jump to bottom

[Alerting] Investigate side effects of long running actions #113424

Closed
ymao1 opened this issue Sep 29, 2021 · 1 comment
Closed

[Alerting] Investigate side effects of long running actions #113424

ymao1 opened this issue Sep 29, 2021 · 1 comment
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Sep 29, 2021

As a corollary to investigating side effects of long running rules, we should also investigate the behavior of long running actions. What happens when an action task times out? Does it get cancelled or does it continue running? What are the implications if it continues running and completes a long while later?
@ymao1 ymao1 added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Actions/Framework Issues related to the Actions Framework estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Sep 29, 2021
This was referenced Oct 1, 2021
Open
Closed
@gmmorris gmmorris added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Oct 6, 2021
@mikecote
Copy link
Contributor

Closing in favour of #123627 as we started implementing some cancellation functionality with #120853.

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gmmorris @kobelb @mikecote @ymao1