influxdata / influxdata/influxdb

Exporting and importing checks does not retain "builder" state

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

Description

See also: https://community.influxdata.com/t/problem-with-import-checkthreshold/19948

When exporting a check via the CLI and then applying it later, the status of the "builder" fields is not retained. The builder fields are used by the UI to display the status of building the check - showing errors if all the necessary selections haven't been made yet. This can result in an imported check showing errors in the UI when it has been properly configured.

In order to fix this, we will likely need a server-side representation of the builder, or some way for the UI to extrapolate it from the query.

Contributor guide

Open the contributing guide

Research direction

Trace the CLI export and apply paths, then inspect the UI code that reads the check's builder fields. Compare an exported check with one created in the UI and determine how the query and builder status are represented. Done means an imported, properly configured check no longer appears to have builder errors.

Written by the indexing model from the issue text.

Assessment

Domain
cli, database, frontend
Issue type
Bug
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.