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

Add priority_key/facility_key options to in_syslog #1351

Merged
merged 1 commit into from
Dec 8, 2016

Conversation

knqyf263
Copy link
Contributor

@knqyf263 knqyf263 commented Dec 6, 2016

I want that priority and facility are in event record.
Currently, I use fluent-plugin-record-reformer to extract priority and facility values from tags.

However, these values have already been parsed in in_syslog plugin.

facility = FACILITY_MAP[pri >> 3]
priority = PRIORITY_MAP[pri & 0b111]

I think it is useless to use another plugin for extracting priority and facility.
Then, I added include_priority/facility options to in_syslog.

@knqyf263 knqyf263 force-pushed the add_options branch 2 times, most recently from ee2b534 to e928ef8 Compare December 6, 2016 07:21
@repeatedly
Copy link
Member

in_tcp's source_hostname_key approach is better than include_priority because someone wants to specify key.

@repeatedly repeatedly added the enhancement Feature request or improve operations label Dec 6, 2016
@knqyf263
Copy link
Contributor Author

knqyf263 commented Dec 6, 2016

@repeatedly Thanks for your feedback!
I fixed. How about this?

@knqyf263 knqyf263 closed this Dec 6, 2016
@knqyf263 knqyf263 reopened this Dec 6, 2016
@knqyf263 knqyf263 changed the title Add include_priority/facility options to in_syslog Add priority_key/facility_key options to in_syslog Dec 6, 2016
@tagomoris
Copy link
Member

LGTM.

@tagomoris tagomoris assigned repeatedly and tagomoris and unassigned repeatedly and tagomoris Dec 7, 2016
@repeatedly repeatedly merged commit 66fb153 into fluent:master Dec 8, 2016
@knqyf263
Copy link
Contributor Author

knqyf263 commented Dec 8, 2016

Thanks!
How about a document?
Shoud I send a PR to fluent/fluentd-docs ? 0.12 or 0.14 ?

@repeatedly
Copy link
Member

I will backport this feature to v0.12 so v0.12 is enough.

@knqyf263
Copy link
Contributor Author

knqyf263 commented Dec 8, 2016

OK!
I sent a PR.
fluent/fluentd-docs#249

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request or improve operations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants