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

[Dashboards] Kuberentes Top CPU Intensive pods visualisation shows error #8957

Closed
ruflin opened this issue Nov 7, 2018 · 5 comments
Closed
Labels
bug containers Related to containers use case Metricbeat Metricbeat module

Comments

@ruflin
Copy link
Contributor

ruflin commented Nov 7, 2018

  • Version: 6.5-Snapshot

After loading the dashboards into Kibana for Kubernetes, the "Top CPU Intensive pods [Metricbeat Kubernetes]" visualisations shows an error (see screenshot below).

screen shot 2018-11-07 at 09 19 35

@ruflin ruflin added bug module Metricbeat Metricbeat containers Related to containers use case labels Nov 7, 2018
@ruflin
Copy link
Contributor Author

ruflin commented Nov 7, 2018

This seems to also affect the system dashboards. @simianhacker you might now more. Looks like the Positive only feature.

@ruflin
Copy link
Contributor Author

ruflin commented Nov 7, 2018

I tested the same with 6.4.3 and the issue does not seem to exist there.

@ruflin
Copy link
Contributor Author

ruflin commented Nov 7, 2018

This is potentially a regression in painless in Elasticsearch. @rjernst might know more here?

@exekias
Copy link
Contributor

exekias commented Nov 7, 2018

As @ruflin said, System dashboard (and maybe others) is affected too This is how it looks:

image

We may need to consider this a blocker. Thoughts?

cc @tsg @monicasarbu @tbragin

tsg added a commit to tsg/kibana that referenced this issue Nov 7, 2018
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.
ruflin pushed a commit to elastic/kibana that referenced this issue Nov 7, 2018
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.
@tsg
Copy link
Contributor

tsg commented Nov 7, 2018

Closing for now, we have elastic/elasticsearch#35351 as a follow up.

@tsg tsg closed this as completed Nov 7, 2018
tsg added a commit to tsg/kibana that referenced this issue Dec 13, 2018
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.
tsg added a commit to elastic/kibana that referenced this issue Dec 15, 2018
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.
exekias pushed a commit to exekias/kibana that referenced this issue Jan 11, 2019
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.
exekias pushed a commit to exekias/kibana that referenced this issue Jan 11, 2019
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.
exekias added a commit to elastic/kibana that referenced this issue Jan 11, 2019
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.
exekias added a commit to elastic/kibana that referenced this issue Jan 11, 2019
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug containers Related to containers use case Metricbeat Metricbeat module
Projects
None yet
Development

No branches or pull requests

3 participants