# Filebeat doesn't send the message field to logstash

**URL:** <https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 19, 2019, 1:16pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398 "2019-07-19T13:16:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniele.saccon](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@daniele.saccon](https://discuss.elastic.co/u/daniele.saccon)\
**Post date:** [July 19, 2019, 1:16pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398/1 "2019-07-19T13:16:08Z")

</div>

Hello,

I have deployed Filebeat 6.8.1 in docker container, filebeat sends all the corrected data but the MESSAGE field is missing.

The input configuration is:

- type: log  
paths:
  - '/var/lib/docker/containers/_/_.log'  
json.message\_key: log  
json.keys\_under\_root: true  
enabled: true  
encoding: utf-8  
fields:  
type: docker\_filebeat\_log  
environment: production  
processors:
  - add\_docker\_metadata: ~

I tried also with input docker, in this case I have the message field but I no longer have the TIME field.

The input configuration is:

- type: docker  
containers.ids: '\*'  
encoding: utf-8  
enabled: true  
exclude\_files: ['.gz$']  
fields:  
type: docker\_filebeat\_log  
environment: production  
processors:
  - add\_docker\_metadata: ~

Can you help me solve one of the two cases?

Thanks

Daniele

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [July 19, 2019, 2:31pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398/2 "2019-07-19T14:31:58Z")

</div>

Hi @daniele.saccon and welcome 🙂

If you are using filebeat to collect docker logs, it'd be better if you try with the second option, using the `docker` input. The `time` field of docker logs is stored as the `@timestamp`.

---

<div class="post-metadata">

**Author:** ![daniele.saccon](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@daniele.saccon](https://discuss.elastic.co/u/daniele.saccon)\
**Post date:** [July 19, 2019, 3:02pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398/3 "2019-07-19T15:02:40Z")

</div>

Hi @jsoriano, thanks 🙂

The @timestamp is overwritten? Is its original value lost?

Thanks

Daniele

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [July 19, 2019, 3:05pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398/4 "2019-07-19T15:05:10Z")

</div>

The time in the logs is used as the `@timestamp`.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 16, 2019, 3:05pm UTC](https://discuss.elastic.co/t/filebeat-doesnt-send-the-message-field-to-logstash/191398/5 "2019-08-16T15:05:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.