influxdata / influxdata/influxdb

Negative conditional expressions are not applied

Open
#23,706 0 comments 0 reactions 0 assignees View on GitHub
area/ui
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. From the UI screen, go to "Alerts: Alerts" -> "NOTIFICATION RULES" and set a negative conditional expression (!=) in "Conditions" Tag Filter.

2. Confirm that the alert is not filtered by the set conditional expression.
(e.g. WHEN A != B)

3. In task edit mode, confirm that the relevant part is not reflected (not **!=**).
(e.g. statuses = monitor["from"](start: -11m, fn: (r) => r["A"] **==** "B"))

__Expected behavior:__
Negative conditional expressions are applied and alerts are properly filtered.

__Actual behavior:__
Negative conditional expressions are not applied and alerts are not filtered.

__Environment info:__
Linux 5.15.32-v8+ aarch64

I have just confirmed a same bug with InfluxDB Cloud.

Finally, I love InfluxDB.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue through Alerts: Alerts → NOTIFICATION RULES with a != tag filter, then inspect the task edit view to compare the generated conditional expression. Done means the negative operator is preserved in the task and alerts are filtered accordingly; the issue does not name a source file or test to run.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.