Hi Samuel, Graylog currently only supports flat message structures, i. e. not nested objects and no lists.
This being said, there's a JSON extractor which can map JSON structures into flat message fields, see http://docs.graylog.org/en/1.3/pages/extractors.html#using-the-json-extractor for details. Has this been an issue for people in real-world use? At least for the Graylog users I know, this hasn't been an issue in the real-world. I'm sure it's nice to have, but it also increases complexity while processing and when writing queries, so I'm not sure that it's actually worth implementing this feature. Cheers, Jochen On Wednesday, 3 February 2016 18:24:40 UTC+1, Samuel Neff wrote: > > Any updates on this four year old request? i'm setting up logging for a > new app and really like Graylog but am getting pushback because of this one > issue. Unfortunately this seems to be an unusual restriction--most other > loggers support complex JSON logging. > > Other than this issue. Graylog looks great. How are others working around > it? Has this been an issue for people in real-world use? > > Thanks, > > Sam > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/ef77f46b-8175-4a51-a90d-345615bf4aa7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
