-
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
[Stack Monitoring] Uncaught exception attempting to load standalone logstash nodes page #123785
Comments
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
Ah. 8.0 works on internal collection (the above 7.16.3 test was internal, the initial bug used metricbeat). Will try to reproduce it on 7.16.3 with metricbeat collection. Sort of wondering now if it was some data issue in my test setup as well. |
Okay, I see what's happening here. The logstash nodes query is hitting
They're not logstash docs so they understandably don't have a UUID. |
main doesn't have this problem since we've removed the |
Kibana version: b2462a6 (8.0 branch head)
Elasticsearch version: 8.0 head
Server OS version: macos
Browser version: chrome
Browser OS version: macos
Original install method (e.g. download page, yum, from source, etc.): source
Describe the bug:
This error is shown when attempting to navigate to standalone logstash nodes page.
Additionally once in this state, navigating via breadcrumbs or back button doesn't help. You need to navigate back to the top of the monitoring app via sidebar or kibana search.
Steps to reproduce:
while :; do echo 'standalone hello' ; sleep 1; done | bin/logstash -e 'input { stdin { } } output { stdout {} }'
)Expected behavior:
Similar node listing/details that we'd get with an elasticsearch output
Screenshots (if relevant):
Cluster overview is good
Logstash overview too
"Nodes" tab explodes
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Console output with
monitoring.ui.debug_mode: true
Any additional context:
Need to check if this also happens on main.
The text was updated successfully, but these errors were encountered: