-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage #52
Comments
@hayatbehlim thank you for opening this issue. I will try to find some time and investigate why this is happening. |
You are welcome @anthonycorbacho , If you need any implementation side help I'm ready for that. |
@hayatbehlim we only parse the first line using with grok, whenever we can. |
What reason is this?I have the same problem @hayatbehlim |
Did you try to use that: https://blog.codecentric.de/en/2017/09/jvm-fire-using-flame-graphs-analyse-performance/ to identify the problem ? |
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
2. https://groups.google.com/forum/#!topic/logstash-users/RB3bBnVp_-c
The text was updated successfully, but these errors were encountered: