Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending custom facility #8

Open
danieljamesscott opened this issue Sep 22, 2015 · 2 comments
Open

Sending custom facility #8

danieljamesscott opened this issue Sep 22, 2015 · 2 comments

Comments

@danieljamesscott
Copy link

What is the recommended replacement for sending the facility, given that the 'facility' field is deprecated?

I see references to 'additional' fields, and 'custom' fields, are these the same thing?

I posted a more detailed question on the logstash forum, but haven't had any replies:

https://discuss.elastic.co/t/configuring-dynamic-facility-with-gelf-output-plugin/28043

@gyger
Copy link

gyger commented Jan 22, 2017

The problem is, that the GELF library (https://github.com/Graylog2/gelf-rb/blob/master/lib/gelf/notifier.rb), has default values set for facility (without underscore). If this value is not set, it is set by the library and then the facility is wrong in graylog2.

@danielfarrelltelit
Copy link

Confirming that this is still broken, nothing seems to have changed on this.
In our environment we have an application that logs to Graylog directly and Graylog honors the facility that is designated by the application, but when the application logs through logstash with the gelf output, the facility is not honored as shown here.

It does not seem hands-tied impossible to fix this, as other applications can seem to log the facility to graylog without issue.
I can provide additional information if it would be considered helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants