influxdata / influxdata/influxdb

Influxdb alters check error

Open
#23,671 0 comments 0 reactions 0 assignees View on GitHub
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. ...Use httpwebrequest from C# to write data to influxdb when an API function is executed(This means the data sending frequency is unexpected.)
2. ...Create Alert to check if a data point is below or above criteria.
3. ...Send alert to Slack if an alter detected

__Expected behavior:__
Should send alters to my slack workplace

__Actual behavior:__
It shows an error **[Last run status :complete(failed)]** when an alert should be triggered in the check section. So, there is no Check history, no Notification history recorded. Nothing sends to Slack either.
However, I have another check rule, which works fine. The only difference is that data is sent with a certain frequency.

__Environment info:__

* System info: Run `uname -srm` and copy the output here : NA
* InfluxDB version: Run `influxd version` and copy the output here : 2.0
* Other relevant environment details: Container runtime, disk info, etc

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the alert check after data is written through the C# HTTP client, then inspect the check execution and Slack notification behavior. The issue provides no logs or named files; done means the check completes successfully, history is recorded, and the alert reaches Slack.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.