# Collecting pod logs after an update

**URL:** <https://community.replicated.com/t/collecting-pod-logs-after-an-update/582>\
**Category:** Supporting your customers\
**Tags:** support, kurl\
**Created:** [October 4, 2021, 12:53pm UTC](https://community.replicated.com/t/collecting-pod-logs-after-an-update/582 "2021-10-04T12:53:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mzs](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/mzs/32/207_2.png) [@mzs](https://community.replicated.com/u/mzs)\
**Post date:** [October 4, 2021, 12:53pm UTC](https://community.replicated.com/t/collecting-pod-logs-after-an-update/582/1 "2021-10-04T12:53:38Z")

</div>

In a kURL cluster, we’re using the `logs` collector to collect pod logs as part of a support bundle. After a software update, or if for any other reason pods were recreated, the previous pod logs tend to be missing. (It’s the same thing I’d see on a bare Kubernetes cluster, where /var/log/pods gets cleaned up as soon as a pod is deleted.)

What are people using to improve log retention on kURL clusters for troubleshooting?