mirror of
https://github.com/elastic/kibana.git
synced 2025-06-28 19:13:14 -04:00
8e7fb7a77e
This PR: - updates navigation instructions to accommodate for the navigation changes related to solution views. - updates instructions for adding sample data to rely on the integrations page instead of the home page, that only exists with the classic solution view - updates references to the home page to avoid confusing users using one of the new solution views Closes: https://github.com/elastic/platform-docs-team/issues/529 Closes: https://github.com/elastic/platform-docs-team/issues/540
114 lines
3.8 KiB
Text
114 lines
3.8 KiB
Text
[role="xpack"]
|
|
[[monitoring-kibana]]
|
|
= Collect monitoring data using legacy collectors
|
|
++++
|
|
<titleabbrev>Legacy collection methods</titleabbrev>
|
|
++++
|
|
|
|
If you enable the Elastic {monitor-features} in your cluster, you can
|
|
optionally collect metrics about {kib}.
|
|
|
|
[IMPORTANT]
|
|
=========================
|
|
{agent} and {metricbeat} are the recommended methods for collecting and shipping
|
|
monitoring data to a monitoring cluster.
|
|
|
|
If you have previously configured legacy collection methods, you should migrate
|
|
to using {agent} or {metricbeat} collection. Do not use legacy collection
|
|
alongside other collection methods.
|
|
|
|
For more information, refer to <<monitoring-elastic-agent>> and
|
|
<<monitoring-metricbeat>>.
|
|
=========================
|
|
|
|
The following method involves sending the metrics to the production cluster,
|
|
which ultimately routes them to the monitoring cluster.
|
|
|
|
To learn about monitoring in general, see
|
|
{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster].
|
|
|
|
. Set the `xpack.monitoring.collection.enabled` setting to `true` on each
|
|
node in the production cluster. By default, it is is disabled (`false`).
|
|
+
|
|
--
|
|
NOTE: You can specify this setting in either the `elasticsearch.yml` on each
|
|
node or across the cluster as a dynamic cluster setting. If
|
|
{stack-security-features} are enabled, you must have `monitor` cluster
|
|
privileges to view the cluster settings and `manage` cluster privileges to
|
|
change them.
|
|
|
|
--
|
|
|
|
** To update the cluster settings in {kib}:
|
|
|
|
... Open {kib} in your web browser.
|
|
+
|
|
--
|
|
By default, if you are running {kib} locally, go to `http://localhost:5601/`.
|
|
|
|
If {security-features} are enabled, log in.
|
|
--
|
|
|
|
... Go to the *Stack Monitoring* page using the
|
|
<<kibana-navigation-search,global search field>>. If data collection is
|
|
disabled, you are prompted to turn it on.
|
|
|
|
** From the Console or command line, set `xpack.monitoring.collection.enabled`
|
|
to `true` on the production cluster. +
|
|
+
|
|
--
|
|
For example, you can use the following APIs to review and change this setting:
|
|
|
|
[source,js]
|
|
----------------------------------
|
|
GET _cluster/settings
|
|
|
|
PUT _cluster/settings
|
|
{
|
|
"persistent": {
|
|
"xpack.monitoring.collection.enabled": true
|
|
}
|
|
}
|
|
----------------------------------
|
|
|
|
For more information, see {ref}/monitoring-settings.html[Monitoring settings in {es}]
|
|
and {ref}/cluster-update-settings.html[Cluster update settings].
|
|
--
|
|
|
|
. Verify that `monitoring.enabled` and
|
|
`monitoring.kibana.collection.enabled` are set to `true` in the
|
|
`kibana.yml` file. These are the default values. For
|
|
more information, see <<monitoring-settings-kb,Monitoring settings in {kib}>>.
|
|
|
|
. Identify where to send monitoring data. {kib} automatically
|
|
sends metrics to the {es} cluster specified in the `elasticsearch.hosts` setting
|
|
in the `kibana.yml` file. This property has a default value of
|
|
`http://localhost:9200`. +
|
|
+
|
|
--
|
|
[TIP]
|
|
===============================
|
|
In production environments, we strongly recommend using a separate cluster
|
|
(referred to as the _monitoring cluster_) to store the data. Using a separate
|
|
monitoring cluster prevents production cluster outages from impacting your
|
|
ability to access your monitoring data. It also prevents monitoring activities
|
|
from impacting the performance of your production cluster.
|
|
|
|
If {security-features} are enabled on the production cluster, use an HTTPS
|
|
URL such as `https://<your_production_cluster>:9200` in this setting.
|
|
===============================
|
|
|
|
--
|
|
|
|
. If {security-features} are enabled on the production cluster:
|
|
|
|
.. Verify that there is a
|
|
valid user ID and password in the `elasticsearch.username` and
|
|
`elasticsearch.password` settings in the `kibana.yml` file. These values are
|
|
used when {kib} sends monitoring data to the production cluster.
|
|
|
|
.. <<configuring-tls-kib-es,Configure encryption for traffic between {kib} and {es}>>.
|
|
|
|
. <<start-stop,Start {kib}>>.
|
|
|
|
. <<monitoring-data,View the monitoring data in {kib}>>.
|