Develop sort of circuit break native in st2
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone, don't know if I'll be able to explain it correctly, but what I want with this is some sort of circuit break natively in stackstorm to prevent some payloads from flooding the system.
For example: In a server, some application X service keeps going down and calling stackstorm for a remediation. What I want is to be able to set a threshold of how many times this is acceptable before stop executing anything and send some notice to the owner that there is a more deep problem that needs attention.
Splunk has more or less the same thing with its alerts, where you can configure it to throttle for couple hours if the problem is still the same as the last execution.

This is something I myself want to develop, but I'd like to discuss it here first. And would appreciate some guidance about where to code it, I've already forked st2 repos into my account.
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
No file, test, or entry point is named. Start by mapping the relevant st2 repositories and event or payload execution paths, then clarify the threshold, repeated-payload matching, suppression period, and owner notification behavior before proposing a design; done means those requirements are specified and covered by tests.
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
- Needs clarification
- Newbie friendliness
- 25/100