You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
It would be nice if some method for gathering metrics about the stack and monitoring its performance were included. Would certainly facilitate troubleshooting. Metricbeat provides an easy way to do this that integrates nicely with the existing setup.
It should also be fairly easy to include as part of the deploy script process. Adding metricbeat logging to the existing deployment only takes (roughly) the following steps:
Install metricbeat on ELK host
metricbeat modules enable elasticsearch
Configure /etc/metricbeat/modules/elasticsearch.yml with information pointing to elasticsearch container and user/password information (which is known by deploy.sh)
Configure /etc/metricbeat/metricbeat.yml with output information to the local elasticsearch or logstash (which is known by deploy.sh)
(May not be necessary) Visit kibana->Stack monitoing to enable montiroing of elasticsearch node
Profit!
The text was updated successfully, but these errors were encountered:
It would be nice if some method for gathering metrics about the stack and monitoring its performance were included. Would certainly facilitate troubleshooting. Metricbeat provides an easy way to do this that integrates nicely with the existing setup.
It should also be fairly easy to include as part of the deploy script process. Adding metricbeat logging to the existing deployment only takes (roughly) the following steps:
The text was updated successfully, but these errors were encountered: