[BUG] alert.suppress parameter is locked in by the Splunk GUI (ES Content Management)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Describe the bug
When a detection which has throttling enabled, is edited with ES Content Management, the value for alert.suppress will be set to 1, instead to true which the jinja2 template sets here.
As a result, the parameter is set in local/savedsearches.conf which locks why further updates that might come through default/savedsearches.conf, using DaC methodology.
Expected behavior
contentctl should follow the "preferences" of whatever the Spunk GUI wants to set.
contentctl Version:
v5.5.9
ES Version:
v7.3.4
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 at contentctl/output/templates/savedsearches_detections.j2 line 82 and inspect how throttled detections are rendered into default/savedsearches.conf and local/savedsearches.conf. Compare the generated alert.suppress value with the Splunk ES GUI representation; done means contentctl preserves the GUI-compatible value without locking later DaC updates.
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
- Mostly clear
- Newbie friendliness
- 48/100