search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.65k stars 8.23k forks source link

kinana 6.6.0 monitor UI nodes not display CPU info #31390

Open imzhulei opened 5 years ago

imzhulei commented 5 years ago

CPU usage AND CPU throttling not display

kibana start with docker， command : docker run -d --restart=always --name kibana --net=host -e ELASTICSEARCH_URL="http://172.16.105.11:9200" docker.elastic.co/kibana/kibana:6.6.0

Elastic Stack version:

plugin:kibana@6.6.0 Ready
  plugin:elasticsearch@6.6.0 Ready
  plugin:xpack_main@6.6.0 Ready
  plugin:graph@6.6.0 Ready
  plugin:monitoring@6.6.0 Ready
  plugin:spaces@6.6.0 Ready
  plugin:security@6.6.0 Ready
  plugin:searchprofiler@6.6.0 Ready
  plugin:ml@6.6.0 Ready
  plugin:tilemap@6.6.0 Ready
  plugin:watcher@6.6.0 Ready
  plugin:grokdebugger@6.6.0 Ready
  plugin:dashboard_mode@6.6.0 Ready
  plugin:logstash@6.6.0 Ready
  plugin:beats_management@6.6.0 Ready
  plugin:apm@6.6.0 Ready
  plugin:interpreter@6.6.0 Ready
  plugin:canvas@6.6.0 Ready
  plugin:license_management@6.6.0 Ready
  plugin:index_management@6.6.0 Ready
  plugin:console@6.6.0 Ready
  plugin:console_extensions@6.6.0 Ready
  plugin:notifications@6.6.0 Ready
  plugin:index_lifecycle_management@6.6.0 Ready
  plugin:infra@6.6.0 Ready
  plugin:rollup@6.6.0 Ready
  plugin:remote_clusters@6.6.0 Ready
  plugin:cross_cluster_replication@6.6.0 Ready
  plugin:upgrade_assistant@6.6.0 Ready
  plugin:metrics@6.6.0 Ready
  plugin:timelion@6.6.0 Ready
  plugin:reporting@6.6.0 Ready

tim 20190218163450

elasticmachine commented 5 years ago

Pinging @elastic/stack-monitoring

cachedout commented 5 years ago

Hi @imzhulei

Do you see the same behavior when not running in Docker?

Containers have special configuration settings for CPU collection: https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html#monitoring-ui-cgroup-settings

imzhulei commented 5 years ago

@cachedout
Thanks for your answer elasticsearch cluster is running in containers. I‘ve configured “xpack.monitoring.ui.container.elasticsearch.enabled: true” in kiabana.yml ,but it still doesn't display cpu usage. I'll check the documentation again to see if elasticsearch.yml needs to be configured

cachedout commented 5 years ago

@imzhulei Do you have CPU throttling applied to your Docker containers? That setting may not be appropriate if you do not.

imzhulei commented 5 years ago

@cachedout

I do not have CPU throttling applied to my elasticsearch Docker containers， if not configured “xpack.monitoring.ui.container.elasticsearch.enabled: true” in kiabana.yml，The nodes page is blank，nothing display。

How to？ thanks.

cachedout commented 5 years ago

@imzhulei If you do not have CPU throttling turned on for containers, then there is no way to for the monitoring application to display CPU usage data.

chrisronline commented 4 years ago

It seems like this is something we should be handling, will label as such

bliles commented 1 year ago

I'm using metricbeat to monitoring the nodes running elasticsearch, if I drill down into the monitoring for an individual node, I see CPU utilization stats for that node, so it seems inconsistent on the main Node list for CPU usage to be N/A. I understand that Elasticsearch's usage and the node's total CPU utilization aren't necessarily the same thing, but perhaps it would at least cause less confusion and be more consistent if the main Node page showed the node's CPU utilization if available?