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

in_syslog: Replace priority_key with proper severity_key #2636

Merged
merged 1 commit into from
Sep 30, 2019

Conversation

repeatedly
Copy link
Member

Signed-off-by: Masahiro Nakagawa [email protected]

Which issue(s) this PR fixes:
None

What this PR does / why we need it:
I noticed priority_key is misleading name because it stores severity, not priority.
So I add proper severity_key and keep priority_key for backward compatibility.
priority_key will be removed at fluentd v2.

Docs Changes:
Will add severity_key and deprecate priority_key

Release Note:
Same as title.

@repeatedly repeatedly added the enhancement Feature request or improve operations label Sep 30, 2019
@repeatedly repeatedly requested a review from ganmacs September 30, 2019 06:54
@repeatedly repeatedly self-assigned this Sep 30, 2019
Copy link
Member

@ganmacs ganmacs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

https://tools.ietf.org/html/rfc5424 says

The number contained within these angle brackets
is known as the Priority value (PRIVAL) and represents both the
Facility and Severity

@repeatedly repeatedly merged commit c23b5c8 into master Sep 30, 2019
@ganmacs ganmacs deleted the in_syslog-proper-name-severity_key branch November 8, 2019 05:03
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.

2 participants