Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dashboard: fill with none for InfluxDB #229

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

DifferentialOrange
Copy link
Member

@DifferentialOrange DifferentialOrange commented Jul 8, 2024

On lower timescales data with fill(null) seems like a scattered set of dots. Data with fill(none) seems fine like a line string. I don't remember these issues on older Grafana versions, so it is possible that something had changed with visualization even for deprecated graph panels.

Before

image

After

image

After #228, Grafana started to use non-existing test artifacts
for startup volumes. This patch fixes the issue.

Follows #228
@DifferentialOrange DifferentialOrange force-pushed the DifferentialOrange/influx-fix-fill branch from ee77298 to 80956a5 Compare July 8, 2024 15:16
On lower timescales data with "fill(null)" seems like a scattered set
of dots. Data with "fill(none)" seems fine like a line string. I don't
remember these issues on older Grafana versions, so it is possible
that something had changed with visualization even for deprecated graph
panels.
@DifferentialOrange DifferentialOrange force-pushed the DifferentialOrange/influx-fix-fill branch from 80956a5 to 4eb6a93 Compare July 8, 2024 15:17
@DifferentialOrange DifferentialOrange marked this pull request as ready for review July 8, 2024 15:17
@DifferentialOrange DifferentialOrange merged commit ffd66fd into master Jul 9, 2024
1 check passed
@DifferentialOrange DifferentialOrange deleted the DifferentialOrange/influx-fix-fill branch July 9, 2024 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants