-
Notifications
You must be signed in to change notification settings - Fork 1.9k
monitore elasticsearch cluster with metricbeat #766
Comments
Hi @ebuildy, |
Yes I understand, Most of Helm charts, have monitoring defined as template , via servicemonitor.yaml: https://github.com/bitnami/charts/blob/master/bitnami/elasticsearch/templates/servicemonitor.yaml. Will be good to have a similar thing with metricbeat. |
Shouldn't we instead have a companion container for each es pod ? so that they are each collected independently ? |
This is not required and not recommended. You should use Metricbeat deployment pod in Metricbeat chart with Elasticsearch module to monitor Elasticsearch. Actually unlike with Prometheus, we don't need anything into Elasticsearch chart for that. The only thing you need is to add the following config into Metricbeat values: deployment:
metricbeatConfig:
metricbeat.yml: |
metricbeat.modules:
- module: elasticsearch
metricsets:
- node
- node_stats
period: 10s
hosts: ["elasticsearch-master:9200"] |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity since being marked as stale. |
Describe the feature:
Some Helm charts, provide monitoring with the application, (the most famous is "prometheus exporter"). By example, https://github.com/bitnami/charts/tree/master/bitnami/elasticsearch .
Since elastic has a product
metricbeat
, what about to propose a metricbeat instance as cluster sideDescribe a specific use case for the feature:
Monitore ES cluster in production.
The text was updated successfully, but these errors were encountered: