-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Parse Failure slows down entire agent #1678
Comments
Hi, For LS 1.5 we have improved the way the Grok filter works and improved the performance by about 2.5 times. Cheers. |
Sadly no... :( |
@galvinograd Any more information you can add like log line, grok config would be helpful here. |
We'll need a bit more information to go on. How do you observe the slowdown? Why do you think some kind of exceptions are the cause? |
For Logstash 1.5.0, we've moved all plugins to individual repositories, so I have moved this issue to logstash-plugins/logstash-filter-grok#41. Let's continue the discussion there! :) |
When logstash fails to parse a large log file with a large grok parse template, it slows down the entire agent's performance significantly. On the other hand, when the parsing succeeds, logstash is orders of magnitude faster.
Maybe it has something to do with exception handling?
The text was updated successfully, but these errors were encountered: