# \_grokparsefailure is occurring even after the grok pattern is success in grokdebugger

**URL:** <https://discuss.elastic.co/t/grokparsefailure-is-occurring-even-after-the-grok-pattern-is-success-in-grokdebugger/280784>\
**Category:** Logstash\
**Created:** [August 9, 2021, 9:26am UTC](https://discuss.elastic.co/t/grokparsefailure-is-occurring-even-after-the-grok-pattern-is-success-in-grokdebugger/280784 "2021-08-09T09:26:50Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Cad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cad/32/86661_2.png) [@Cad](https://discuss.elastic.co/u/Cad)\
**Post date:** [August 13, 2021, 10:16am UTC](https://discuss.elastic.co/t/grokparsefailure-is-occurring-even-after-the-grok-pattern-is-success-in-grokdebugger/280784/15 "2021-08-13T10:16:12Z")

</div>

Hi vaseemQA,

> [@vaseemQA](#):
>
> My understanding is, the event json took total 2 records and parsed/transformed/processed it in 39 milliseconds which is basically 39/2 = 19.5 milliseconds for each document

I think so, just to be more precise, it's an average per event

> [@vaseemQA](#):
>
> Also, can you please tell me the difference between these
> 
> > duration\_in\_millis
> 
> Vs
> 
> > queue\_push\_duration\_in\_millis

I never use this API but according to the documentation, `queue_push_duration_in_millis` seems to be related to [Persistent queues](https://www.elastic.co/guide/en/logstash/current/persistent-queues.html#persistent-queues).

[This answer](https://discuss.elastic.co/t/measuring-the-taking-time/113900/4) from a previous topic seems pretty accurate about what they means and about my understanding from the documentation.

Sorry for not being able to be more helpful on this subject

Cad.

---

_[View the full topic](https://discuss.elastic.co/t/grokparsefailure-is-occurring-even-after-the-grok-pattern-is-success-in-grokdebugger/280784)._