Monitoring Logstash (Legacy)
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Stack
Generally available
Use the Elastic Stack monitoring features to gain insight into the health of Logstash instances running in your environment. For an introduction to monitoring your Elastic stack, see Monitoring a cluster in the Elasticsearch Reference. Then, make sure that monitoring is enabled on your Elasticsearch cluster.
These options for collecting Logstash metrics for stack monitoring have been available for a while:
- Metricbeat collection. Metricbeat collects monitoring data from your Logstash instance and sends it directly to your monitoring cluster. The benefit of Metricbeat collection is that the monitoring agent remains active even if the Logstash instance does not.
- Legacy collection (deprecated). Legacy collectors send monitoring data to your production cluster.
For more features, dependability, and easier management, consider using:
- Elastic Agent collection for Stack Monitoring. Elastic Agent collects monitoring data from your Logstash instance and sends it directly to your monitoring cluster, and shows the data in Logstash Dashboards. The benefit of Elastic Agent collection is that the monitoring agent remains active even if the Logstash instance does not, you can manage all your monitoring agents from a central location in Fleet.