influxdata / influxdata/kapacitor

Match expressions Discrepancy between documentation and implementation

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

Description

In the docs https://docs.influxdata.com/kapacitor/v1.5/working/alerts/#match-expressions it is mentioned " The data that triggered the alert is available to the match expression, including all fields and tags."

But in the implementation only tags are available for match and not fields
https://github.com/influxdata/kapacitor/blob/v1.5.6/services/alert/handlers.go#L531

Please acknowledge the bug and let me know if PR's are welcomed because I wanted to use fields in match expressions , especially previouslevel "PreviousLevel: e.previousState.Level"

Contributor guide

Open the contributing guide

Research direction

Start by comparing the match-expression documentation with services/alert/handlers.go at line 531, where the issue reports that only tags are available. Trace how alert data reaches match expressions and determine the intended behavior for fields, including the requested PreviousLevel use. Done means the implementation matches the documented availability or the documentation clearly reflects the supported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.