# Custom pattern problems in the grok filter

**URL:** https://discuss.elastic.co/t/custom-pattern-problems-in-the-grok-filter/26221
**Category:** Logstash
**Created:** [July 24, 2015, 8:41am UTC](https://discuss.elastic.co/t/custom-pattern-problems-in-the-grok-filter/26221 "2015-07-24T08:41:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 24, 2015, 8:14pm UTC](https://discuss.elastic.co/t/custom-pattern-problems-in-the-grok-filter/26221/2 "2015-07-24T20:14:00Z")

</div>

For the record, this was sorted out here:

> [@Get the right timestamp for old log files](https://discuss.elastic.co/t/get-the-right-timestamp-for-old-log-files/24943/57):
>
> Okay. You have a single grok filter with multiple expressions. With the default true value of [break\_on\_match](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#plugins-filters-grok-break_on_match) grok will stop once it gets a match. You need to disable that or split your multi-expression grok filter into two separate filters.

---

_[View the full topic](https://discuss.elastic.co/t/custom-pattern-problems-in-the-grok-filter/26221)._