-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decoding nested JSON objects #3
Labels
Comments
@luckyb56 what you want ? decode in single message or multiple message? |
@pramodanarase A single message would be great as it will keep the context and do basic level of stats. |
+1 |
joschi
pushed a commit
to Graylog2/graylog2-server
that referenced
this issue
Nov 21, 2016
Some messages may contain objects as field values, and we need to properly convert them into strings that can be rendered by react. This commit changes the way we convert values into strings, relying on `JSON.stringify()` to do it. Refs Graylog2/graylog-plugin-beats#3
This has been partially addressed in Graylog2/graylog2-server#3106 and #29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using Packetbeat to send messages directly to Graylog2, the nested JSON objects won't be decoded and would be seen as '[object Object],[object Object]' under search UI. Example input JSON message:
packetbeat_dns_answers structure won't be decoded in this example.
The text was updated successfully, but these errors were encountered: