-
Notifications
You must be signed in to change notification settings - Fork 339
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
automatic origin element #225
Comments
Hello, I'd like to work on this issue. Can you please assign me? |
Sure, you are welcome to work this one of you'd like. |
Origin structure data element is basically 4 optional fields for Syslog Protocol:
It is clear what to put in 2 fields:
|
Yes, all of the fields in the origin element should be configurable. The default for the IP param(s) could be either the first network address found when querying or all of the addresses on the machine; the RFC includes both options as something application MAY do. For the sake of simplicity, perhaps we start with the first address in this change, and update it later. As you build this out, be sure that you're using the existing functionality where possible. Perhaps a new public function to get the origin |
hey @az1plo. I am sorry, just noticed the issue is assigned to you! |
RFC 5424 specifies that a
origin
structured data element may be included to give some level of information about the originator of the log message. Stumpless should have the ability to generate this element automatically, as well as the capability to include it automatically when logging to given targets.The text was updated successfully, but these errors were encountered: