influxdata / influxdata/influxdb

Check status and notification search box suggested queries don't work.

Open
#20,784 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug monitoring-and-alerting severity/sev-4 team/ui team/unity v2-prod-bug
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. Create a check named "my check"
2. Let it run so that check statuses are recorded.
3. Observe that results for that check are stored in the `_monitoring` bucket's `statuses` measurement.
4. Observe that results for that check show up on the check status history page, as long as you don't run any searches.
5. Click the search box and type the suggested query, `"check" == "my check"`

__Expected behavior:__
I expect the history of my check to show up.

__Actual behavior:__
Nothing shows up when running the suggested queries. The actual, correct syntax (discerned from watching the HTTP requests sent by the search) is `"checkName" == "my check"`.

Note also that the same sort of issue occurs for notification history; the suggested query is `"notification rule" == "my rule"`, but the correct query is `"notificationRuleName" == "my rule"`.

__Environment info:__
* InfluxDB version: InfluxDB Cloud 2.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in InfluxDB Cloud by creating a check and a notification rule, then use the check status and notification history search boxes. Compare the suggested queries with the requests sent by each search and trace where those suggestions are generated. Done means both suggestions use the field names accepted by their respective history searches and return the expected results.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, search
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.