# Grok filtering not happening

**URL:** <https://discuss.elastic.co/t/grok-filtering-not-happening/178863>\
**Category:** Logstash\
**Created:** [April 29, 2019, 8:30am UTC](https://discuss.elastic.co/t/grok-filtering-not-happening/178863 "2019-04-29T08:30:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ltom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ltom/32/45704_2.png) [@ltom](https://discuss.elastic.co/u/ltom)\
**Post date:** [April 29, 2019, 8:30am UTC](https://discuss.elastic.co/t/grok-filtering-not-happening/178863/1 "2019-04-29T08:30:12Z")

</div>

I have two docker containers running, [docker.elastic.co/beats/filebeat:7.0.0](http://docker.elastic.co/beats/filebeat:7.0.0) running Filebeat, and sebp/elk:latest running ELK stack. The goal is to have my nginx logs in Kibana.

The Filebeat container is sending the nginx logs to the ELK container using [this yml file](https://github.com/spujadas/elk-docker/blob/master/nginx-filebeat/filebeat.yml). The logs appear in Kibana, but there's still an unparsed message field.

I was under the impression that [this config file](https://github.com/spujadas/elk-docker/blob/master/11-nginx.conf) is supposed to apply [this pattern](https://github.com/spujadas/elk-docker/blob/master/nginx.pattern) on the message field.

Does someone here know what might be going wrong and how to fix it?

---

<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:** [May 27, 2019, 8:30am UTC](https://discuss.elastic.co/t/grok-filtering-not-happening/178863/2 "2019-05-27T08:30:15Z")

</div>

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