-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Fix Cluster Listing view #103718
[Monitoring] Fix Cluster Listing view #103718
Conversation
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
@neptunian can you log a ticket that references this one, for us to investigate why this return value seems to be slightly malformed in the first place?
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
15 similar comments
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
2 similar comments
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
⏳ Build in-progress, with failures
To update your PR or re-run it, just comment with: cc @neptunian |
@elasticmachine merge upstream |
@elasticmachine run elasticsearch-ci/docs |
* check for number of nodes * remove console Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @neptunian |
Summary
Resolves #102090
When there is more than one cluster and no nodes exist on the cluster, the page does not load. A good place to test this is using Edge and trying to access Stack Monitoring. The view should look like this: