[BUG] alert.digest_mode should be dynamic in savedsearches_detections.j2
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Describe the bug
v4.4.0 introduced the feature to define throttling for detections:
throttling:
period: 3600s #time period to throttle
fields: name,host # fields to throttle on
but for this to work alert.digest_mode has to be set to 0 when the fields key is defined, as per docs.
Expected behavior
The value for alert.digest_mode should be dynamic when the fields key is defined.
Screenshots
If applicable, add screenshots to help explain your problem.
contentctl Version:
v5.5.9
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
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 in contentctl/output/templates/savedsearches_detections.j2 at the alert.digest_mode setting referenced in the issue, and review how the throttling fields are rendered. Verify the generated saved-search configuration for detections with and without throttling fields; done means alert.digest_mode changes appropriately when fields is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100