By default, the Monitoring application is enabled, but data collection
is disabled. When you first start {kib} monitoring, you are prompted to
enable data collection. If you are using {security}, you must be
signed in as a user with the cluster:manage
privilege to enable
data collection. The built-in superuser
role has this privilege and the
built-in elastic
user has this role.
You can adjust how monitoring data is
collected from {kib} and displayed in {kib} by configuring settings in the
kibana.yml
file. There are also monitoring.ui.elasticsearch.*
settings,
which support the same values as {kib} configuration settings.
To control how data is collected from your {es} nodes, you configure
{ref}/monitoring-settings.html[xpack.monitoring.collection
settings] in elasticsearch.yml
. To control how monitoring data is collected
from Logstash, configure monitoring settings in logstash.yml
.
For more information, see {ref}/monitor-elasticsearch-cluster.html[Monitor a cluster].
|
Set to |
|
Specifies the location of the {es} cluster where your monitoring data is stored.
By default, this is the same as |
|
Specifies the username used by {kib} monitoring to establish a persistent connection
in {kib} to the {es} monitoring cluster and to verify licensing status on the {es}
monitoring cluster. |
|
Specifies the password used by {kib} monitoring to establish a persistent connection
in {kib} to the {es} monitoring cluster and to verify licensing status on the {es}
monitoring cluster. |
|
Specifies the time in milliseconds to wait for {es} to respond to internal
health checks. By default, it matches the |
These settings control how data is collected from {kib}.
|
Set to |
|
Specifies the number of milliseconds to wait in between data sampling on the
{kib} NodeJS server for the metrics that are displayed in the {kib} dashboards.
Defaults to |
These settings adjust how the {kib} Monitoring page displays monitoring data. However, the defaults work best in most circumstances. For more information about configuring {kib}, see {kibana-ref}/settings.html[Setting Kibana Server Properties].
|
Specifies the number of log entries to display in the Monitoring UI. Defaults to
|
|
Specifies the number of term buckets to return out of the overall terms list when
performing terms aggregations to retrieve index and node metrics. For more
information about the |
|
Specifies the minimum number of seconds that a time bucket in a chart can
represent. Defaults to 10. If you modify the
|
|
Set to |
The Monitoring UI exposes the Cgroup statistics that we collect for you to make better decisions about your container performance, rather than guessing based on the overall machine performance. If you are not running your applications in a container, then Cgroup statistics are not useful.
|
For {es} clusters that are running in containers, this setting changes the
Node Listing to display the CPU utilization based on the reported Cgroup
statistics. It also adds the calculated Cgroup CPU utilization to the
Node Overview page instead of the overall operating system’s CPU
utilization. Defaults to |
|
For {ls} nodes that are running in containers, this setting
changes the {ls} Node Listing to display the CPU utilization
based on the reported Cgroup statistics. It also adds the
calculated Cgroup CPU utilization to the {ls} node detail
pages instead of the overall operating system’s CPU utilization. Defaults to |