influxdata / influxdata/kapacitor

Feature Request: Trigger alert based on result of previous alert

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

Description

This should address below scenario.

Say we have configured **tick** script to alert(email for ex) if node goes down. There might be two reasons for node going down. One, telegraf agent is down. Two, node itself is down. In this case we want to evaluate what is the reason for node going down.

Here, we can configure ` .exec` and run some script to analyze the node failure and then return some result back to Kapacitor and then Kapacitor should alert based on the result received.

This would be a cool feature if implemented.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing Kapacitor's .exec behavior and how alert results are currently evaluated. Trace how a script result could be returned to an alert rule, then define tests for distinguishing a down Telegraf agent from a down node and triggering the corresponding alert. Done means the requested result-based alert flow is specified and covered by tests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.