Grok support for extractors #377
Closed
Comments
|
+∞ |
+1 |
Grok conversion (int and float) could be also implemented. E.g. %{NUMBER:num:int} or %{NUMBER:amount:float} |
+1 |
kroepke
added a commit
that referenced
this issue
Jan 8, 2015
…e result fields, even if they happen to produce just one #377
kroepke
added a commit
to graylog-labs/graylog2-web-interface
that referenced
this issue
Jan 8, 2015
those aren't supported right now so we turn them off Graylog2/graylog2-server#377
kroepke
added a commit
that referenced
this issue
Jan 9, 2015
kroepke
added a commit
to graylog-labs/graylog2-web-interface
that referenced
this issue
Jan 9, 2015
…do anything with them * not showing is enough because the rest api won't give out any information and the page would be empty anyway, so it's not necessary to make the controller inaccessible Graylog2/graylog2-server#377
Can you add default's patterns (as logstash do : https://github.com/elasticsearch/logstash/tree/v1.4.0/patterns) ? |
kroepke
added a commit
to graylog-labs/graylog2-web-interface
that referenced
this issue
Jan 13, 2015
* more minor layout cleanup * some other minor text changes Graylog2/graylog2-server#377
@sebclick we will likely not ship with default patters, but you can now import pattern files with two clicks. that will be available in beta.2 |
@kroepke Nice |
has been implemented in way too many commits. |
Brilliant feature, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When it comes to parsing complex (read:crappy) log formats Jordan Sissel hit a homerun with the concepts and ideas behind Grok.
I have tried plain regex'es and drools but neither can match the ease, speed, and maintainability of grok patterns.
As a bonus it would enable a lot of transparency between Logstash and Graylog2.
Parsing crappy syslog like this :
took 2 minutes using something like this :
The text was updated successfully, but these errors were encountered: