# Best blueprint/architecture/best practice to monitor Logstash pipelines with alerts in Kibana?

**URL:** <https://discuss.elastic.co/t/best-blueprint-architecture-best-practice-to-monitor-logstash-pipelines-with-alerts-in-kibana/265677>\
**Category:** Logstash\
**Tags:** elastic-stack-alerting\
**Created:** [February 27, 2021, 3:57am UTC](https://discuss.elastic.co/t/best-blueprint-architecture-best-practice-to-monitor-logstash-pipelines-with-alerts-in-kibana/265677 "2021-02-27T03:57:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![byteandbit](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@byteandbit](https://discuss.elastic.co/u/byteandbit)\
**Post date:** [February 27, 2021, 3:57am UTC](https://discuss.elastic.co/t/best-blueprint-architecture-best-practice-to-monitor-logstash-pipelines-with-alerts-in-kibana/265677/1 "2021-02-27T03:57:31Z")

</div>

Hello,  
We are looking for best practice to monitor our Logstash (several pipelines with various input and output plugins) and alert via Slack or eMail in case of problems. Do we just read Logstash logs? If so again whats the best practice in case of k8s deployment? We are currently on 7.11 across ELK (self managed) running on GCP.  
Thanks,  
Bog

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 27, 2021, 3:58am UTC](https://discuss.elastic.co/t/best-blueprint-architecture-best-practice-to-monitor-logstash-pipelines-with-alerts-in-kibana/265677/2 "2021-03-27T03:58:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.