Issues
- Exception in filter permanently stop logstash (for at least one input)LOGSTASH-1797Logstash Developers
- mutate:typeLOGSTASH-1745Jason Kendall
- Mutate:replace displays incorrect output on stdoutLOGSTASH-1177Resolved issue: LOGSTASH-1177Philippe Weber
- Add newline with gsubLOGSTASH-985Resolved issue: LOGSTASH-985Logstash Developers
- Mutate: cannot remove a deep fieldLOGSTASH-941Resolved issue: LOGSTASH-941Jordan Sissel
5 of 5
It seems that when you have a filter with a mutate that in turn has a doubly nested rename target, e.g. mutate { rename => [ "ProcessName", "[eventlog][process_name]" ] }, then you get exceptions if the incoming json_lines-encoded message contains that property/field and its value is a Number (in JSON) instead of a string.
Below is a listing of the stack-trace and relevant code.
It seems that we can reliably reproduce the crash below if we let the mutate stanza work on a string with double backslashes:
Stacktrace
[no further events]
event.rb
fieldreference.rb