# Filebeat Kubernetes autodiscover with post "processor" specific field with another filebeat module

**URL:** <https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 5, 2023, 3:29am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503 "2023-01-05T03:29:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 6, 2023, 3:44pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/6 "2023-01-06T15:44:36Z")

</div>

Do you mean the filebeat nginx module directly read the access/error log file?

Or something like this? [NGINX Ingress controller + Filebeat with NGINX module - Elastic Stack / Beats - Discuss the Elastic Stack](https://discuss.elastic.co/t/nginx-ingress-controller-filebeat-with-nginx-module/291824)

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503)._