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

ui: details tooltip picks out uneven data points #23480

Closed
couchand opened this issue Mar 6, 2018 · 1 comment
Closed

ui: details tooltip picks out uneven data points #23480

couchand opened this issue Mar 6, 2018 · 1 comment
Labels
A-webui-timeseries C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. X-stale
Milestone

Comments

@couchand
Copy link
Contributor

couchand commented Mar 6, 2018

It looks like the details tooltip just picks out the closest datapoint in each series to the cursor, which has very unintuitive behavior around series for started/stopped nodes. Example:

screen shot 2018-03-06 at 11 44 13 am

The first recorded datapoint for nodes that were started minutes later is picked up when hovering over the start of this chart (which you can see by the huge dot that gets added to the hovered points), which makes it seem like, for instance, n5 had 19 replicas at 16:28, when in fact it didn't exist.

@couchand couchand added the S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. label Mar 6, 2018
@couchand couchand added this to the 2.1 milestone Mar 6, 2018
@couchand couchand added A-webui-timeseries C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. and removed S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. labels Apr 24, 2018
@nstewart nstewart added the S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. label Sep 18, 2018
@couchand couchand modified the milestones: 2.1, 2.2 Oct 1, 2018
@github-actions
Copy link

github-actions bot commented Jun 7, 2021

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
5 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-webui-timeseries C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. X-stale
Projects
None yet
Development

No branches or pull requests

2 participants