Stackstorm rate-limiting feature for workflow and host level
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
(Copied manually from https://github.com/StackStorm/st2contrib/issues/647, original reporter https://github.com/sibirajal)
We have configured multiple rules/workflows/actions for our infrastructure monitoring alerts to perform the auto remediation with ST2.
The workflows are created for different alerts and we would like to have some rate limiting at workflow level and individual host level to avoid the continues remediation. If we have this feature in Stackstorm will help us to avoid masking of the real issues.
For example:
Scenario 1: host level
The disk alert appeared in the monitoring for serverX and St2 performed the remediation at 10 am. Same disk alert appeared in the monitoring for serverX at 10:08 am and St2 shouldn't perform the remediation. It should have some rate limiting feature to avoid the continues remediation.
Scenario 2: workflow level
The disk alert appeared in the monitoring for serverX and st2 performed the remediation at 10 am using the disk_remediation_workflow.
The disk alert appeared in the monitoring for serverY and st2 performed the remediation at 10:15 am. Again the disk alert appeared in the monitoring for serverZ and st2 performed the remediation at 10:20 am. In this case we would like to have some rate limiting at workflow level to avoid the infinite time execution.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing StackStorm's rule, action, and workflow execution paths, using the copied st2contrib issue and the disk_remediation_workflow scenarios as requirements. Determine how workflow-level and host-level rate limits should be configured and enforced, then verify that repeated alerts are suppressed independently for the same host and across hosts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100