Feature request: Rule tester + full logs.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
There's st2-rule-tester to see if a rule will be triggered or not on an event.
Sometimes a rule is triggered, but you see "ERROR: log [-] Failed kicking off execution for rule RuleDB [...]" in the logs.
The error is actually cut off and the full message is not shown, which makes the troubleshooting more difficult.
It would be really nice to have a similar tester that would show if the rule can actually execute well.
Having full logs is also something that I find necesary.
It would be nice if the data from the ERROR was formatted properly, with indentations and line returns, instead of being an "oneliner"
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 st2-rule-tester and the rule execution error logs. Define how a tester should report whether a rule can execute, then determine how full, properly formatted error messages should be exposed. Done means both requested behaviors have clear, testable outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100