Skip to content

Commit

Permalink
docs(elasticsearch-module): specify metricsets behaviour with x-pack …
Browse files Browse the repository at this point in the history
…mode enabled (#39612)

Co-authored-by: Marco Antonio Ghiani <[email protected]>
  • Loading branch information
tonyghiani and Marco Antonio Ghiani authored May 22, 2024
1 parent a8c806e commit 96f4afc
Show file tree
Hide file tree
Showing 2 changed files with 28 additions and 0 deletions.
14 changes: 14 additions & 0 deletions metricbeat/docs/modules/elasticsearch.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,20 @@ UI in {kib}. To enable this usage, set `xpack.enabled: true` and remove any `met
from the module's configuration. Alternatively, run `metricbeat modules disable elasticsearch` and
`metricbeat modules enable elasticsearch-xpack`.

When xpack mode is enabled, all the legacy metricsets are automatically enabled by default.
This means that you do not need to manually enable them, and there will be no conflicts or issues because Metricbeat merges the user-defined metricsets with the ones that xpack mode forces to enable.
As a result, you can seamlessly collect comprehensive metrics without worrying about dataset overlap or duplication.

[source,yaml]
----
metricbeat.modules:
- module: elasticsearch
xpack.enabled: true
metricsets:
- ingest_pipeline
period: 10s
----

NOTE: When this module is used for {stack} Monitoring, it sends metrics to the
monitoring index instead of the default index typically used by {metricbeat}.
For more details about the monitoring index, see
Expand Down
14 changes: 14 additions & 0 deletions metricbeat/module/elasticsearch/_meta/docs.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,20 @@ UI in {kib}. To enable this usage, set `xpack.enabled: true` and remove any `met
from the module's configuration. Alternatively, run `metricbeat modules disable elasticsearch` and
`metricbeat modules enable elasticsearch-xpack`.

When xpack mode is enabled, all the legacy metricsets are automatically enabled by default.
This means that you do not need to manually enable them, and there will be no conflicts or issues because Metricbeat merges the user-defined metricsets with the ones that xpack mode forces to enable.
As a result, you can seamlessly collect comprehensive metrics without worrying about dataset overlap or duplication.

[source,yaml]
----
metricbeat.modules:
- module: elasticsearch
xpack.enabled: true
metricsets:
- ingest_pipeline
period: 10s
----

NOTE: When this module is used for {stack} Monitoring, it sends metrics to the
monitoring index instead of the default index typically used by {metricbeat}.
For more details about the monitoring index, see
Expand Down

0 comments on commit 96f4afc

Please sign in to comment.