# Grok parse failures

**URL:** <https://discuss.elastic.co/t/grok-parse-failures/257230>\
**Category:** Logstash\
**Created:** [December 1, 2020, 3:34pm UTC](https://discuss.elastic.co/t/grok-parse-failures/257230 "2020-12-01T15:34:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [December 1, 2020, 4:12pm UTC](https://discuss.elastic.co/t/grok-parse-failures/257230/4 "2020-12-01T16:12:21Z")

</div>

Sometimes DATA will [not do](https://discuss.elastic.co/t/doubts-about-grok/257129/2) what you expect. You might be better off with a custom pattern

```
<?(Type)[^|]*>

```

will match anything that is not a pipe character.

---

_[View the full topic](https://discuss.elastic.co/t/grok-parse-failures/257230)._