monitore elasticsearch cluster with metricbeat
See original GitHub issueDescribe 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 side
Describe a specific use case for the feature:
Monitore ES cluster in production.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Collecting Elasticsearch monitoring data with Metricbeat
Collecting Elasticsearch monitoring data with Metricbeatedit · Install Metricbeat. · Enable the Elasticsearch module in Metricbeat on each Elasticsearch node.
Read more >Collecting Elasticsearch monitoring data with Metricbeat
Create a user on the monitoring cluster that has the remote_monitoring_agent built-in role. · Add the username and password settings to the Elasticsearch...
Read more >4-ELK Stack: Configure metricbeat 7.x to monitor elasticsearch ...
To monitor elasticsearch cluster services, Metricbeat can be installed on the edge server where services are running; it provides you with the ...
Read more >Getting started with Metricbeat. How to monitor system metrics ...
Metricbeat is a lightweight agent that can be installed on target servers to periodically collect metric data from your target servers, this could...
Read more >metricbeat monitoring of Elasticsearch and Kibana broke on ...
Generally speaking you want to maintain "cluster config" in metricbeat.yml : elasticsearch credentials, kibana, security, etc. and modules ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Shouldn’t we instead have a companion container for each es pod ? so that they are each collected independently ?
This issue has been automatically closed because it has not had recent activity since being marked as stale.