-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Dashboards] Kuberentes Top CPU Intensive pods visualisation shows error #8957
Comments
This seems to also affect the system dashboards. @simianhacker you might now more. Looks like the |
I tested the same with 6.4.3 and the issue does not seem to exist there. |
This is potentially a regression in painless in Elasticsearch. @rjernst might know more here? |
As @ruflin said, System dashboard (and maybe others) is affected too This is how it looks: We may need to consider this a blocker. Thoughts? |
It's at the moment unclear if this is a Painless regression (looks like), but this seems to fix it based on testing. I'm doing this change in the 6.5 branch, for a couple of reasons: I tested it in 6.5 only, because master didn't seem to exhibit this issue. And it is not the right fix, if Painless has a true regression. Closes elastic/beats#8957.
It's at the moment unclear if this is a Painless regression (looks like), but this seems to fix it based on testing. I'm doing this change in the 6.5 branch, for a couple of reasons: I tested it in 6.5 only, because master didn't seem to exhibit this issue. And it is not the right fix, if Painless has a true regression. Closes elastic/beats#8957.
Closing for now, we have elastic/elasticsearch#35351 as a follow up. |
This is a loose forward-port of elastic#25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
This is a loose forward-port of #25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
This is a loose forward-port of elastic#25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
This is a loose forward-port of elastic#25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
This is a loose forward-port of #25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
This is a loose forward-port of #25307, which was rushed in for 6.5. I created this PR to make sure we don't lose the fix. Part of #elastic/beats#8957.
After loading the dashboards into Kibana for Kubernetes, the "Top CPU Intensive pods [Metricbeat Kubernetes]" visualisations shows an error (see screenshot below).
The text was updated successfully, but these errors were encountered: