# Keeping \`message\` field intact with module parsing

**URL:** <https://discuss.elastic.co/t/keeping-message-field-intact-with-module-parsing/155452>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 5, 2018, 8:12pm UTC](https://discuss.elastic.co/t/keeping-message-field-intact-with-module-parsing/155452 "2018-11-05T20:12:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rocketraman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rocketraman/32/32342_2.png) [@rocketraman](https://discuss.elastic.co/u/rocketraman)\
**Post date:** [November 6, 2018, 2:46pm UTC](https://discuss.elastic.co/t/keeping-message-field-intact-with-module-parsing/155452/3 "2018-11-06T14:46:50Z")

</div>

@kvch Sorry, I didn't specify: this is with filebeats running inside Kubernetes, with auto-discover enabled and hints on. The example logs I gave a screenshot above was with a pod annotated with:

```auto
co.elastic.logs/module: apache2
co.elastic.logs/fileset: access

```

---

_[View the full topic](https://discuss.elastic.co/t/keeping-message-field-intact-with-module-parsing/155452)._