influxdata / influxdata/kapacitor

[feature request] cross checks dependencies

Open
#682 3 comments 0 reactions 0 assignees View on GitHub
new-feature
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Hi,

It would be really great if there was a way to connect checks in some sort of dependencies tree. It's especially important with integrations like PagerDuty or any other external services. It is really hard to imagine reason to send 10+ alerts to PagerDuty if 9+ alerts are result of the first one. Because kapacitor is triggering those alerts I think it's the right place to implement dependencies between them. It is possible right now to workaround that with an additional table in influxdb and store there information about alerts but it's a workaround. More native way for dependencies would be great.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how Kapacitor triggers alerts and handles external services such as PagerDuty. Define how checks would be represented in a dependency tree and how downstream alerts should behave when an upstream alert fires. Done should provide a native dependency mechanism that avoids sending redundant alerts.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability-sre
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.