# Pushing different types of (access, application) logs using filebeat-daemonset in Kubernetes

**URL:** https://discuss.elastic.co/t/pushing-different-types-of-access-application-logs-using-filebeat-daemonset-in-kubernetes/261353
**Category:** Beats
**Tags:** filebeat
**Created:** [January 17, 2021, 3:58pm UTC](https://discuss.elastic.co/t/pushing-different-types-of-access-application-logs-using-filebeat-daemonset-in-kubernetes/261353 "2021-01-17T15:58:07Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### 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: [January 18, 2021, 8:45am UTC](https://discuss.elastic.co/t/pushing-different-types-of-access-application-logs-using-filebeat-daemonset-in-kubernetes/261353/2 "2021-01-18T08:45:00Z")

</div>

The common practice is to involve the ingest node pipeline. See this thread: [Best practice for Logging with Filebeat](https://discuss.elastic.co/t/best-practice-for-logging-with-filebeat/131479/2)

---

_[View the full topic](https://discuss.elastic.co/t/pushing-different-types-of-access-application-logs-using-filebeat-daemonset-in-kubernetes/261353)._