# Filebeat daemon set misses last few lines of log on pod crash

**URL:** <https://discuss.elastic.co/t/filebeat-daemon-set-misses-last-few-lines-of-log-on-pod-crash/286640>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 13, 2021, 3:14pm UTC](https://discuss.elastic.co/t/filebeat-daemon-set-misses-last-few-lines-of-log-on-pod-crash/286640 "2021-10-13T15:14:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TimWardFS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timwardfs/32/65108_2.png) [@TimWardFS](https://discuss.elastic.co/u/TimWardFS)\
**Post date:** [October 13, 2021, 3:14pm UTC](https://discuss.elastic.co/t/filebeat-daemon-set-misses-last-few-lines-of-log-on-pod-crash/286640/1 "2021-10-13T15:14:30Z")

</div>

I have seen a number of posts saying that when a Kubernetes pod crashes Filebeat loses the last few lines of log output, including, of course, the actual error message that tells you why the pod crashed.

All the ones I've found have timed out and been closed.

Is any action being taken on this bug?

---

<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:** [November 10, 2021, 5:15pm UTC](https://discuss.elastic.co/t/filebeat-daemon-set-misses-last-few-lines-of-log-on-pod-crash/286640/2 "2021-11-10T17:15:08Z")

</div>

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