vjeantet/grok issues and pull requests

#37 - fix: mutex added while accessing aliases map

Pull Request - State: open - Opened by nityanandagohain almost 2 years ago

#36 - when I add a custom pattern wich starts with "(?<"， I run into "error parsing regexp: invalid or unsupported Perl syntax: `(?<`"

Issue - State: open - Opened by arloor almost 2 years ago

#35 - Grok.Parser() Nested Fields support

Issue - State: open - Opened by SanjayNagBR over 2 years ago

#34 - Custom Pattern Grok Parse not working

Issue - State: open - Opened by SanjayNagBR over 2 years ago

#33 - concurrent map read and map write

Issue - State: closed - Opened by zhlicen over 3 years ago

#32 - Fix regex for dependency handling

Pull Request - State: closed - Opened by srebhan almost 4 years ago - 3 comments

#31 - Improve error handling

Pull Request - State: closed - Opened by srebhan almost 4 years ago - 2 comments

#30 - Failing in AMD64

Issue - State: open - Opened by genisysram almost 4 years ago

#29 - Add support for envoy common access logs

Pull Request - State: closed - Opened by nitishm about 5 years ago

#28 - Add envoy common access log to grok/patterns.go

Issue - State: closed - Opened by nitishm about 5 years ago

#27 - field names with dots

Issue - State: open - Opened by maja42 about 5 years ago - 2 comments

#26 - Fix parse typed with alias

Pull Request - State: closed - Opened by tengattack over 5 years ago - 2 comments

#25 - Fields with brackets

Issue - State: open - Opened by pete-leese over 6 years ago - 4 comments

#24 - When using a custom pattern with dot in name, parse intermittently fails with "no pattern found"

Issue - State: closed - Opened by danielnelson over 6 years ago

#23 - Added support for field names containing '-' and '.'

Pull Request - State: closed - Opened by aantono over 6 years ago - 3 comments

#22 - multiline support

Issue - State: closed - Opened by ganting almost 7 years ago - 2 comments

#21 - please version grok

Issue - State: closed - Opened by aviau about 7 years ago - 3 comments

#20 - Improve performance of parallel operations

Pull Request - State: closed - Opened by arnecls about 7 years ago - 2 comments

#19 - Export the Grok.compile and Grok.compiledparse ?

Issue - State: closed - Opened by buixor about 7 years ago - 1 comment

#18 - Fixed #17, short patterns not replaced with regex

Pull Request - State: closed - Opened by jamesofnet over 7 years ago - 2 comments

#17 - Issue using grok %{IPORHOST} pattern

Issue - State: closed - Opened by sparrc almost 8 years ago - 2 comments

#16 - Match failed when the field has '-'

Issue - State: closed - Opened by ebookbug about 8 years ago - 1 comment

#15 - Cache compiled regexps and add ParseStream function

Pull Request - State: closed - Opened by paulstuart over 8 years ago - 4 comments

#14 - ref #13

Pull Request - State: closed - Opened by logrusorgru over 8 years ago

#13 - AddPatternsFromMap panics if any of the internal pattern does not exist

Issue - State: closed - Opened by logrusorgru over 8 years ago - 1 comment

#12 - replace compiledin default patterns with only "base" ones

Issue - State: closed - Opened by vjeantet about 9 years ago - 1 comment

#11 - Task/refactor parse typed

Pull Request - State: closed - Opened by macvaz about 9 years ago - 2 comments

#10 - Add Type to semantic

Issue - State: closed - Opened by palmerabollo over 9 years ago - 22 comments

#9 - Parse funcs should follow the default set behavior, and can not be changed.

Issue - State: closed - Opened by vjeantet over 9 years ago

#8 - Setting global options when creating the Grok instance.

Issue - State: closed - Opened by vjeantet over 9 years ago - 2 comments

#7 - rename constants in the form of "DefaultCapture", not "DEFAULTCAPTURE"

Issue - State: closed - Opened by vjeantet over 9 years ago - 3 comments
Labels: wontfix

#6 - refactor the way grok add a new pattern from a path or using AddPattern