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 On Saturday, March 10, 2012 at 7:41:32 AM UTC-5, Sean Bannister wrote: > > I asked over on ServerFault > <http://serverfault.com/questions/363315/graylog2-can-a-custom-gelf-field-accept-a-json-object> > > if the GELF spec <https://github.com/Graylog2/graylog2-docs/wiki/GELF> > supported JSON objects on custom fields. At the moment this doesn't appear > to be the case but I see a number of use cases where this could be useful > when logging complex data structures. Lennart mentioned I should start a > discussion. > > In my Node.js application I have a function that converts my stack traces > to JSON objects so they're easy to read but also in a format that I can > programatically process this is a great example of something that works > well as a JSON object. But any complex data structure that you need to log > would work best as a JSON object, we could then query on these complex > objects and get much more out of our reporting. > > Loggly does something similar to this and its well worth a read > http://loggly.com/blog/2011/06/on-the-way-to-impressive/ > -- 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/211486bb-5b85-4ed8-9932-215925b49e8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
