[graylog2] Re: Adds graylog2 some fields itself?

2014-08-21 Thread ellyas ellyas
Someone answer to my simple question PLEASE! :( -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https:

[graylog2] Re: Why can't we set per-input extractors on inputs running on radios?

2014-08-21 Thread Pierre Rousset
Same issue/question here, we are unable to use radio because of this limitation! On Tuesday, August 19, 2014 6:07:01 PM UTC+9, J John wrote: > > Hey all, > Hi devs, > > I just noticed that if I create a (Kafka) radio input and open an input on > the radio (syslog/plaintext UDP and so on), I cann

Re: [graylog2] Re: Adds graylog2 some fields itself?

2014-08-21 Thread Brantley Hobbs
ellyas, The specification (http://graylog2.org/gelf#specs) indicates that "version" MUST be set by the client and so is probably required. The other two are optional. I would guess that your logging library is adding them. You might try to see if the library has a mechanism to stop supplying th

Re: [graylog2] Adds graylog2 some fields itself?

2014-08-21 Thread Martin Schütte
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.08.2014 15:52, ellyas ellyas wrote: > But in graylog2 after GELF input add a few fields with constant > values like "version" ( 1.0 ), "facility" ( gelf-rb ) and "level" ( > info[6] ). > > How to get rid of these unwelcome fields me? These fiel

Re: [graylog2] Adds graylog2 some fields itself?

2014-08-21 Thread ellyas ellyas
> >These fields are added by logstash, or more precisely the gelf-rb > >module used to format GELF messages. They are added because they are > >required fields according to the GELF 1.0 spec. Did you probably mean values of that fields, but not fields itself? I have tried to use Syslog UDP