Parsing multi-line logs use high cpu near to 100%. There is no way to find out which grok filter taking more cpu cycle and How we can optimize it. This issue looks similar to logstash grok issue 1.[https://gist.github.com/jordansissel/4646783](https://gist.github.com/jordansissel/4646783) 2. [https://groups.google.com/forum/#!topic/logstash-users/RB3bBnVp_-c](https://groups.google.com/forum/#!topic/logstash-users/RB3bBnVp_-c)
Activity
anthonycorbacho commentedon Jun 13, 2016
@hayatbehlim thank you for opening this issue.
I will try to find some time and investigate why this is happening.
hayatbehlim commentedon Jun 15, 2016
You are welcome @anthonycorbacho , If you need any implementation side help I'm ready for that.
retoo commentedon Jul 28, 2017
@hayatbehlim we only parse the first line using with grok, whenever we can.
ShawshankLin commentedon Mar 22, 2019
What reason is this?I have the same problem @hayatbehlim
fbacchella commentedon Mar 22, 2019
Did you try to use that: https://blog.codecentric.de/en/2017/09/jvm-fire-using-flame-graphs-analyse-performance/ to identify the problem ?