influxdata / influxdata/kapacitor
Feature request: add/remove UDF through API/CLI without restarting Kapacitor.
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
As more and more alert requirements come to us, there is need to add/remove UDF to support these requirements frequently.
However, by modifying the UDF nodes in configuration file and restarting the Kapacitor, the existing alerts will be affected. We would like to have a more comfortable way to do this.
Thanks:)
Contributor guide
Research direction
Start by tracing the API and CLI entry points for UDF configuration and the configuration-file handling for UDF nodes. Define how add and remove operations should work at runtime, then verify that existing alerts remain unaffected without restarting Kapacitor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100