influxdata / influxdata/kapacitor

Is it possible to force an Alert to change state with HTTP?

Open
#2,698 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Hello,

I have been trying to dig into the source code of Kapacitor, trying to find a way to force change the state of an Alert without inserting new points to influxdb.

The idea would be to create a custom endpoint (if needed) in Kapacitor and provide the ID of an Alert in the request as well as the desired state. From there, what would be a possible way to access said Alert and change its state directly?

It is still unclear how AlertNodes are managed in the code but I gather that it is impossible to change the state of an Alert by creating an AlertState and calling the Point function with a custom point as the AlertState is not linked to a node.

Thank you in advance for any help you can provide.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Kapacitor source around AlertNodes, AlertState, and the Point function, which the issue identifies as the relevant concepts. Determine whether an HTTP endpoint can locate an alert by ID and change its state without new InfluxDB points; done means documenting a feasible design or confirming the limitation and its required scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.