Jochen Schalanda

Since Graylog 1.2.0, we ship a [JSON Extractor](http://docs.graylog.org/en/1.2/pages/extractors.html#using-the-json-extractor) which can be used to "expand" a JSON payload received as plaintext into a proper GELF message. You can read in the...

We designed the Graylog Collector exactly the other way round. The goal was to do as little preprocessing on the client machines as possible and move that complexity into the...

@et304383 We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our [discussion forum](https://community.graylog.org/) or join the [#graylog...

@mohanrao The Graylog Collector has been deprecated. I recommend using nxlog or filebeat to ingest text files and them to Graylog.

@mohanrao Logstash (using JRuby and thus running on AIX) could be another viable replacement in this case.

@mohanrao Please move this discussion to our [public mailing list](https://groups.google.com/forum/#!forum/graylog2) or join the [#graylog channel on freenode IRC](https://webchat.freenode.net/?channels=%23graylog). Thank you!

@jt55401 Yes, we'll phase out the Graylog Collector. I'd recommend using nxlog or winlogbeat to collect Windows Eventlogs and nxlog or filebeat to collect files.

@sonnylaskar Please attach the MIB file.

Thanks for reporting this! The file you've mentioned (`.\logs\graylog-collector-stdout`) is simply the log output of the Graylog Collector itself and doesn't contain any of the processed and sent log messages...

@ackstorm23 See https://www.graylog.org/post/introducing-graylog-labs