EDR Report graph axis contains undesirable choices

Open
#2,198 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
html
Domain
cli, data-visualization

Research direction

Start by reproducing the issue with edr report using a row-count volume test and time-series data in the thousands, then inspect how the volume and anomaly graphs choose Y-axis labels. Done means the axis values are visually distinct and intuitive instead of repeating or using confusing rounded values such as 1K.

Written by the indexing model from the issue text.

Description

Bug Stale Triage 👀

Describe the bug
Axis values in the volume and anomaly graphs generated by 'edr report' are often hard to read or rounded to strange values. For example see the screenshot attached. The Y axis of this graph contains 981, 1K, 1K and 2K as values for the Axis however the rounded 1K attributes are non-standard. The very first graph point has a value of 1537, it seems the line is maybe suppose to represent 1600 as a plot further down is 1621 and is above the line and a 1589 seems almost on the line. Mousing over the Y axis doesn't say what the line value is.

To Reproduce

  1. Enabled a row count volume test
  2. Generate data that spans into the thousands of rows and make multiple time series recordings
  3. View graph in the volume section

Expected behavior
The Axis values should be visually distinct and intuitive 1K, 1.6K, and 2k is hard to mentally work with.

Screenshots
Image

Environment (please complete the following information):

  • Elementary CLI (edr) version: 0.23.2
  • Elementary dbt package version: 0.23.0
  • dbt version you're using latest
  • Data warehouse: Redshift

Would you be willing to contribute a fix for this issue?
Not at this time

Dominant language
HTML
Stars
2.4k
Forks
226
Avg merge
1d 21h
Merged PRs (30d)
20

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.

More from elementary-data/elementary

All issues in elementary-data/elementary

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.