Jochen Schalanda

@darouwan Please provide the complete log message (and some context around it) and ideally a minimal project to reproduce the issue.

@MarkusMcNugen > `org.graylog.plugins.pipelineprocessor.functions.ips.IpAddress["anonymized"]` Is this the literal log output or did you replace the actual IP address with "anonymized"? If the latter, please provide a *real* IP address which triggers...

@hc4 Thanks for reporting this! For now, you can either use named parameters *or* unnamed parameters for all arguments of a function. Example: ``` parse_date(str, "yyyy-MM-dd HH:mm:ss", "en", "UTC"); parse_date(value:...

@lennartkoopmann I think the `abbreviate()` function should really just abbreviate the input string and not replace it entirely. Would it help to have a `str_length()` function which returns the length...

@gianluca-valentini Yes, `errors` is supposed to be a read-only field and not part of the payload. This being said, Graylog shouldn't throw an error if the `errors` field is set.

@thomasdarimont FYI, the syntax used in this plugin is *not* identical to the Drools syntax.

How about `retain_fields()` (similar to the nomenclature in [`CharMatcher`](http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/base/CharMatcher.html))?

Possible solutions: * Add a message loader to the pipeline simulator, similar to the extractors page, to load an existing message and simulate its run through the pipelines. * Store...

> ``` > when > parse_date(value:$message.log_date, pattern:"MMM dd HH:mm:ss.SSS", timezone:"CET"); > then > // ... > end > ``` Apart from the semicolon in the `when` block which syntactically isn't...

> The rule would be the option to manipulate the date - if a specific date string is found. The aspect of user experience aside, why can't you use a...