vjeantet / grok

simple library to use/parse grok patterns with go (100%)

vjeantet/grok Issues

when I add a custom pattern wich starts with "(?<"， I run into "error parsing regexp: invalid or unsupported Perl syntax: `(?<`"
Updated 2 years ago
Custom Pattern Grok Parse not working
Updated 3 years ago
Grok.Parser() Nested Fields support
Updated 3 years ago
concurrent map read and map write
Closed 3 years ago
field names with dots
Updated 4 years ago2
Export the Grok.compile and Grok.compiledparse ?
Closed 4 years ago1
Add envoy common access log to grok/patterns.go
Closed 4 years ago
When using a custom pattern with dot in name, parse intermittently fails with "no pattern found"
Closed 4 years ago
Failing in AMD64
Updated 4 years ago
Fields with brackets
Updated 6 years ago4
Match failed when the field has '-'
Closed 7 years ago1
multiline support
Closed 7 years ago2
please version grok
Closed 7 years ago3
Issue using grok %{IPORHOST} pattern
Closed 7 years ago2
AddPatternsFromMap panics if any of the internal pattern does not exist
Closed 8 years ago1
replace compiledin default patterns with only "base" ones
Closed 8 years ago1
Add Type to semantic
Closed 9 years ago22
Setting global options when creating the Grok instance.
Closed 9 years ago2
rename constants in the form of "DefaultCapture", not "DEFAULTCAPTURE"
Closed 9 years ago3
Parse funcs should follow the default set behavior, and can not be changed.
Closed 9 years ago
return only named captures when parsing
Closed 9 years ago9
refactor the way grok add a new pattern from a path or using AddPattern
Closed 9 years ago