-
Notifications
You must be signed in to change notification settings - Fork 5k
Closed
Labels
Description
We are currently working on a solution that will allow users to use Metricbeat to monitor the Elastic stack. The first piece of this is to try and use Metricbeat to monitor Kibana.
The idea is that metricbeat will create exactly the same documents in .monitoring-kibana-* indices as Kibana's bulk uploader does today. In order to verify that this parity is indeed maintained at all times, we should write an automated system test that will do something like the following:
- Start up Elasticsearch (with the default Basic license is okay)
- Enable Monitoring in Elasticsearch (via the cluster setting
xpack.monitoring.collection.enabled: true) - Start up Kibana (with the default Basic license is okay)
- Let Kibana run for ~20 seconds so a few documents are indexed into
.monitoring-kibana-*. - Stop Kibana
- From
.monitoring-kibana-*, retrieve a document each fortype = kibana_statsandtype = kibana_settings. - Delete the
.monitoring-kibana-*indices. - In
kibana.yml, setxpack.monitoring.kibana.collection.enabled: false. - Start up Kibana again.
- Enable the
kibanamodule with thestatsandsettingsmetricsets in metricbeat. - Set
xpack.enabled: truein themodules.kibanasection inmetricbeat.yml. - Start metricbeat.
- Let metricbeat run for ~20 seconds so a few documents are indexed into
.monitoring-kibana-*. - Stop metricbeat
- From
.monitoring-kibana-*, retrieve a document each fortype = kibana_statsandtype = kibana_settings. - Compare the documents retrieved indexed by Kibana's with those indexed by metricbeat. Verify that their structures are identical (same fields, not necessarily same values).