# Provided Grok patterns do not match data in the input

**URL:** <https://discuss.elastic.co/t/provided-grok-patterns-do-not-match-data-in-the-input/270265>\
**Category:** Logstash\
**Created:** [April 15, 2021, 3:20pm UTC](https://discuss.elastic.co/t/provided-grok-patterns-do-not-match-data-in-the-input/270265 "2021-04-15T15:20:44Z")\
**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:** [April 15, 2021, 5:18pm UTC](https://discuss.elastic.co/t/provided-grok-patterns-do-not-match-data-in-the-input/270265/4 "2021-04-15T17:18:03Z")

</div>

> [@Cris\_R](#):
>
> does it means that the debugger works differently from the routine ?

I have certainly seen cases where kibana and the Heroku debugger parse things differently to logstash (kibana does multiline matching of GREEDYDATA differently, for example). I do not use them, instead I debug grok patterns using grok as detailed [here](https://discuss.elastic.co/t/help-needed-in-grok/213827/2).

---

_[View the full topic](https://discuss.elastic.co/t/provided-grok-patterns-do-not-match-data-in-the-input/270265)._