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

[Monitoring] Address some UI regressions with shard allocation #29757

Conversation

chrisronline
Copy link
Contributor

@chrisronline chrisronline commented Jan 31, 2019

Fixes #29753
Fixes #20772

During the EUI migration, we had some UI regressions in the Elasticsearch shard allocation UI.

This PR fixes those. See the issue for more details.

screen shot 2019-01-31 at 3 06 05 pm

TODO

  • Add tests

@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@chrisronline chrisronline requested a review from a team as a code owner January 31, 2019 20:07
@chrisronline
Copy link
Contributor Author

Related to #20772

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Design changes here look good.

Copy link
Member

@pickypg pickypg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One core comment.

const classes = calculateClass(shard);
const color = getColor(classes);
const classification = classes + ' ' + shard.shard;

let shardUi = (
<EuiTextColor color={color}>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this color code working? In the screenshot, the color doesn't match any of the badge colors. Perhaps the shardUi should be a badge instead of a dark block of text with a color that may not show well on that background?

@elasticmachine
Copy link
Contributor

💔 Build Failed

@ryankeairns
Copy link
Contributor

@chrisronline not related, but perhaps something you can tackle here... I just added a note in another issue #29100 (comment) about a hex value in _shard_allocation.scss. Perhaps you can remove (if unused) or change that in this PR and close that dark mode issue?

@ryankeairns
Copy link
Contributor

@chrisronline I see that this PR is failing for the same reason as a backport PR I have open (for the design changes that were merged to master) - #29764.

My original PR passed, but these are not, and that particular test appears to go into a pending state when run locally. Any ideas on how to resolve it?

@chrisronline
Copy link
Contributor Author

@ryankeairns I removed the hex and am looking into the test failures.

@pickypg Good suggestion. I'm not sure the colors are the best. Any thought?

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@chrisronline
Copy link
Contributor Author

retest

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@chrisronline
Copy link
Contributor Author

@ryankeairns The test looks flaky and I'm not sure why. This PR now passes and I think maybe the UI changes we made removed the flakliness. Once this is merged and backported, maybe you can merge 6.x into your backport branch and try CI again

@ryankeairns
Copy link
Contributor

@chrisronline I'll give that a shot, thank you!

Copy link
Member

@pickypg pickypg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I don't have any good suggestions for colors, and I suspect our past dependence on them bites us for colorblind users anyway. We should probably look at replacing this entire shard "view" with something else and preferably as its own table per node / index so that it can take up more space and show more information (like symbols + shard ID rather than just colors + shard ID).

@chrisronline chrisronline merged commit fba727b into elastic:master Feb 4, 2019
@chrisronline chrisronline deleted the monitoring/fix_shard_allocation_ui_regressions branch February 4, 2019 20:15
@ryankeairns
Copy link
Contributor

@chrisronline do you have a backport open for this one? That will get my own backport PR unblocked by the flaky test. Thanks!

@chrisronline
Copy link
Contributor Author

@ryankeairns Just opened! #29993

chrisronline added a commit that referenced this pull request Feb 4, 2019
@chrisronline
Copy link
Contributor Author

Backport:
6.x: 15147b9

@chrisronline
Copy link
Contributor Author

This never made it into 6.6.1 FYI

chrisronline added a commit to chrisronline/kibana that referenced this pull request Feb 25, 2019
chrisronline added a commit that referenced this pull request Feb 25, 2019
@chrisronline
Copy link
Contributor Author

6.6 backport: 7660ee0

@sinzin91
Copy link

sinzin91 commented Mar 6, 2019

Is this going to be fixed in 6.6.2? How do I uptake the backport?

@chrisronline
Copy link
Contributor Author

@sinzin91 This is slated for the next patch release of 6.6. Keep an eye out for our next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants