Closed henrikjohansen closed 8 years ago
Unfortunately (or rather fortunately) I can't reproduce this on Graylog 1.2.2.
@henrikjohansen Is the full_message
field only invalid in some cases or all the time? Are those messages correctly stored in Elasticsearch, including a valid full_message
document field?
Maybe some external GELF client already transmits those invalid contents ("[object Object]", which looks like the JavaScript notation of a stringified complex object).
@joschi the full_message field is present and can also be selected as a field to run extractors against - it's merely a display issue.
@henrikjohansen Ah, ok. It seems only to happen on the Extractor page. I've tried to reproduce the bug on the search page and on the streams page. Should've read the issue title in the first place. :wink:
This was fixed in the linked PRs, and also on master.
After upgrading to v1.2.2 the full_message field is no longer displayed correctly - instead the page only shows "full_message [object Object]"