JSON Extractor fails to convert to fields when there are fields with null value #1475
Comments
@gvagenas Could you please elaborate on the problem and maybe add a concrete example to the issue? |
@joschi see bellow a json message that contains null values:
When trying to extract fields with a JSON extractor the "Try!" button gives me all the fields as expected and the ones with null values comes with just the key:
Noticed the property Now even like this when I save the extractor, I see no extracted fields, not even the one that have values. After applying the patch #1476 it will come with: Thanks |
Mapping a JSON Please check your Graylog server logs for error messages (maybe a |
@joschi, there are no NPE at server log. George |
Also, I agree on the semantics of null, the patch I provided was a quick hack that maybe can provide hints for where is the problem |
Currently evaluating GL as we're not happy with CloudWatch logging & JSON, and this is kind of a blocker. |
The issue has been fixed and will be in the upcoming Graylog 1.2.2 release. |
Thanks @bernd . Do you have a ETA for the 1.2.2 release? I have a blog post ready for how to use Graylog with Restcomm (www.restcomm.com) and waiting the 1.2.2 release. Regards |
@gvagenas Graylog 1.2.2 is being released as we speak. |
Thats great :) Congrats guys |
Working with the latest 1.2.1.
Even though when testing with "Try" I can see all the fields, even the ones with null value, the extractor doesn't convert the string to fields.
I believe the fields with null value should be extracted with string "null" instead of null value
The text was updated successfully, but these errors were encountered: