# Has anyone built an end to end process on log forwarding to log pruning?

**URL:** <https://discuss.elastic.co/t/has-anyone-built-an-end-to-end-process-on-log-forwarding-to-log-pruning/187673>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 26, 2019, 8:32pm UTC](https://discuss.elastic.co/t/has-anyone-built-an-end-to-end-process-on-log-forwarding-to-log-pruning/187673 "2019-06-26T20:32:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryan\_stuhlsatz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bryan_stuhlsatz/32/49123_2.png) [@bryan\_stuhlsatz](https://discuss.elastic.co/u/bryan_stuhlsatz)\
**Post date:** [June 26, 2019, 8:32pm UTC](https://discuss.elastic.co/t/has-anyone-built-an-end-to-end-process-on-log-forwarding-to-log-pruning/187673/1 "2019-06-26T20:32:58Z")

</div>

Has anyone built an end to end process on log forwarding to log pruning?  
Or, does everyone keep several x days of logs on the source, just in case something happens and you have to re-forward. Then implement watcher rules to ensure that data is flowing in and call it good?

Scenario.  
Filebeats collects logs from a directory. It sends the data to logstash/elastic. Data validation is done in elastic, and the log is then pruned on the source.

---

<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:** [July 24, 2019, 8:33pm UTC](https://discuss.elastic.co/t/has-anyone-built-an-end-to-end-process-on-log-forwarding-to-log-pruning/187673/2 "2019-07-24T20:33:00Z")

</div>

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