# Filebeat Ingests K8S Older Logs **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [April 12, 2021, 9:21pm UTC](https://discuss.elastic.co/t/filebeat-ingests-k8s-older-logs/269950 "2021-04-12T21:21:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![danielc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielc/32/78486_2.png) [@danielc](https://discuss.elastic.co/u/danielc)\ **Post date:** [April 12, 2021, 9:21pm UTC](https://discuss.elastic.co/t/filebeat-ingests-k8s-older-logs/269950/1 "2021-04-12T21:21:45Z")
I'm using [beats/filebeat-kubernetes.yaml at v7.8.1 · elastic/beats · GitHub](https://github.com/elastic/beats/blob/v7.8.1/deploy/kubernetes/filebeat-kubernetes.yaml) to ingest K8S. There have been 2 issues: 1. Filebeat picks up older logs when there is an other application deployment and generates old indices like filebeat-2021.03.01 etc. (index: filebeat-%{+YYYY.MM.dd} 2. Filebeat misses some logs from the new pods unless I terminate Filebeat pods. I think that the timestamp in filebeat-%{+YYYY.MM.dd} is from system rather than from the log file. Isn't it? ---
**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\ **Post date:** [April 13, 2021, 8:15am UTC](https://discuss.elastic.co/t/filebeat-ingests-k8s-older-logs/269950/2 "2021-04-13T08:15:06Z")
Could you share some sample logs with us? I suspect that there might be a timestamp conversion problem. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 11, 2021, 10:15am UTC](https://discuss.elastic.co/t/filebeat-ingests-k8s-older-logs/269950/3 "2021-05-11T10:15:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.