Daijiro Fukuda

I have fixed this in * #4106

> The root cause of this is that sometimes the Ruby library does not parse a given string as `Hash`. > > ```ruby > require "json" > JSON.load('"hoge"') > =>...

We need to consider carefully the specification of the case where raw data can not be parsed as `Hash`. I think the currently intended usecases are `Hash` or `Array` of...

```xml @type sample tag test.hash sample {"message": "{\"k\":\"v\"}"} @type sample tag test.string sample {"message": "\"HELLO\""} @type sample tag test.array sample {"message": "[{\"k\":\"v\"}, {\"k2\":\"v2\"}]"} @type parser key_name message @type json @type...

This will be fixed in #4106. There are still some points that need to be done in #4106. I will fix it so that it can be included in the...

The remaining problem is `filter_parser` can't return multiple parsed results since #4474. From #4478 > The following problem of `filter_parser` remains in #4474 : > > > However, we have...

> `null_value_pattern unchanged` should produce: > > ``` > {msg: "foo"} > ``` > > ### Expected behavior > > Field with value `unchanged` should be discarded. No. The expected...

What happens actually? Please share the actual result.

> Note: no `log_error`, so a `null` value doesn't create a field. I think it is not the specification of Parser plugin. Some other settings may discard the key o...

In addition, the following setting with `null_value_pattern` works as expected. ```xml @type tail tag test path /path/to/test.log read_from_head true @type none @type parser key_name message reserve_data true remove_key_name_field true inject_key_prefix...