-
Notifications
You must be signed in to change notification settings - Fork 449
Add syslog protocol fields to event #301
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -195,3 +195,32 @@ | |
| This is mainly useful if you use more than one system that assigns | ||
| risk scores, and you want to see a normalized value across all systems. | ||
| - name: facility | ||
| level: core | ||
| type: long | ||
| example: 1 | ||
| description: > | ||
| Value parsed from messages adhering to RFC 5424 or RFC 3164. | ||
| It represents the process the event has originated from. | ||
| - name: facility_label | ||
| level: extended | ||
| type: keyword | ||
| example: kernel | ||
| description: > | ||
| Human readable format of `event.facility`. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rather than "Human readable", can we add "text-based" or something similar? Humans can read numbers too :-) |
||
| - name: priority | ||
| level: core | ||
| type: long | ||
| example: 1 | ||
| description: > | ||
| Value parsed from messages adhering to RFC 5424 or RFC 3164. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Enhance this definition to something like: "The priority of the event. Typically associated with syslog priority for events adhering to RFC 5424 or RFC 3164." |
||
| - name: priority_label | ||
| level: extended | ||
| type: keyword | ||
| example: Informational | ||
| description: > | ||
| Human readable format of `event.priority`. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rather than "Human readable", can we add "text-based" or something similar? Humans can read numbers too :-)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The I don't think there is such a thing as a priority label in Syslog. The priority number is the one made up of I think we need to remove this field. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enhance this definition to something like: "The facility or process from which the event originated. Typically associated with syslog facility for events adhering to RFC 5424 or RFC 3164."