# Tips and Best Practices for working / debugging Logstash pipelines on Kubernetes **URL:** \ **Category:** Logstash\ **Created:** [August 17, 2020, 4:31pm UTC](https://discuss.elastic.co/t/tips-and-best-practices-for-working-debugging-logstash-pipelines-on-kubernetes/245280 "2020-08-17T16:31:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Xavier\_Krantz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavier_krantz/32/59812_2.png) [@Xavier\_Krantz](https://discuss.elastic.co/u/Xavier_Krantz)\ **Post date:** [August 17, 2020, 4:31pm UTC](https://discuss.elastic.co/t/tips-and-best-practices-for-working-debugging-logstash-pipelines-on-kubernetes/245280/1 "2020-08-17T16:31:28Z")
Hi everyone 👋 I have setup a `BLEK` (Beats, Logstash, ElasticSearch, Kibana) stack on Kubernetes 😛 I would like to parse and enrich some logs output from my services collected through `Filebeat`. Have you some tips and best-practices for working and iterating with `Logstash` pipelines ? By example, I am wondering how to get `Filebeat` "raw" message sent to `Logstash` to be able to work with Grok debugger and define my filter rules ? In the same way, how can I deploy my new rule but still be sure I do not lose any event ? Naively, I was thinking about duplicating the stream: - 1 copy use the previous flow - 1 copy use my new defined flow and gets somewhere where I can validate it works as expected before deleting the previous flow Thank you all for your tips and suggestions 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 14, 2020, 4:31pm UTC](https://discuss.elastic.co/t/tips-and-best-practices-for-working-debugging-logstash-pipelines-on-kubernetes/245280/2 "2020-09-14T16:31:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.