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

[Stack Monitoring] [Test Scenario] Consistent UX across stack products #98777

Open
3 tasks done
phillipb opened this issue Apr 29, 2021 · 3 comments
Open
3 tasks done

Comments

@phillipb
Copy link
Contributor

phillipb commented Apr 29, 2021

Summary

We need to ensure each stack product has a consistent experience and there is consistency between stack products.

Testing

samples

Screen Shot 2020-10-08 at 1 47 49 PM

Screen Shot 2020-10-08 at 1 48 41 PM

@phillipb phillipb added Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services test-plan labels Apr 29, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

@estermv estermv self-assigned this Apr 30, 2021
@estermv
Copy link
Contributor

estermv commented Apr 30, 2021

All overview pages have status section, but for APM seems that there is missing some information:
Screenshot 2021-04-30 at 15 13 41

Not sure if it's a bug or I need to configure something else.

Another thing that I noticed is that some table cells have a bigger font-size than others:

  • On the nodes list table:

Screenshot 2021-04-30 at 15 17 06

  • In the kibana instances table:

Screenshot 2021-04-30 at 15 16 18

Is this intended?

@smith smith added Team:Monitoring Stack Monitoring team and removed Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services labels Nov 13, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/infra-monitoring-ui (Team:Monitoring)

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

No branches or pull requests

5 participants