Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extending the alerting API to reload kapacitor tasks due to changed alerting rules #980

Closed
Patrick-Eichhorn opened this issue Jan 22, 2021 · 0 comments · Fixed by #982
Closed

Extending the alerting API to reload kapacitor tasks due to changed alerting rules #980

Patrick-Eichhorn opened this issue Jan 22, 2021 · 0 comments · Fixed by #982
Assignees
@Patrick-Eichhorn
Labels
area/config-server enhancement New feature or request

Comments

@Patrick-Eichhorn
Copy link
Contributor

Actually, if alerting rules in the configuration server are updated, a restart of kapacitor is required to enable the changes in the kapacitor tasks.
An API call to kapacitor can trigger a reload of the tasks at runtime, to avoid a restart of kapacitor.
@Patrick-Eichhorn Patrick-Eichhorn self-assigned this Jan 22, 2021
@Patrick-Eichhorn Patrick-Eichhorn changed the title Extending the Alerting API to reload kapacitor tasks due to changed alerting rules Extending the alerting API to reload kapacitor tasks due to changed alerting rules Jan 22, 2021
@Patrick-Eichhorn Patrick-Eichhorn mentioned this issue Jan 26, 2021
Merged
Patrick-Eichhorn added a commit that referenced this issue Feb 2, 2021
@Patrick-Eichhorn
Closes #980 - Extending the alerting API to reload kapacitor tasks du…
f2bf2d0 
…e to changed alerting rules (#982)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Patrick-Eichhorn Patrick-Eichhorn

Labels
area/config-server enhancement New feature or request
Projects
None yet
Milestone
No milestone
1 participant
@Patrick-Eichhorn