Exception in Grok Plugin about logstash-filter-grok HOT 7 OPEN

Can anyone please confirm if the fix is correct?

Is the bug mentioned anywhere? I am not seeing a description of the bad behavior, so I'm not quite able to assess your proposed change.

from logstash-filter-grok.

@jordansissel - apologies. I was away for a while. This is a bug that got triggered through logstash in my deployment. I tracked it to this function. However the exception is happening through grok?. I am assuming that's a problem?

from logstash-filter-grok.

@nipunarora What exception? Can you show me a stack trace?

from logstash-filter-grok.

@jordansissel : I get this exception output from grok, how can I generate a stack trace? Seems like the stack trace is not really being generated, even though an exception is trigerred. I turned on --debug option in logstash:

1078 {:timestamp=>"2016-01-08T15:02:04.787000-0500", :message=>"Grok regexp threw exception", :exception=>"63", :level=>:warn, :file=>"logstash/filters/grok.rb", :line=>"332"}

from logstash-filter-grok.

The exception message being '63' is ... confusing me. You'll have to modify the code to get a stack trace. Line 332 of logstash/filters/grok.rb is what prints the log message for your version of logstash, so that'd be a place to start. You can get the stack trace as e.backtrace

from logstash-filter-grok.

If you still experience this on newer releases of Logstash, can you provide a sample config and a sample input text that triggers the exception?

from logstash-filter-grok.

I do see the exception in the current version of logstash as well. I'll try and see if I can provide a small test-case since I've a particularly large config file with several patterns.

@jordansissel - Please find the debug output using the backtrace here:
https://gist.github.com/nipunarora/766ad7f411aca6f3a40a

from logstash-filter-grok.