-
Notifications
You must be signed in to change notification settings - Fork 350
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
syslog: T6989: convert old configuration format to "advanced" #4305
Conversation
👍 |
✅ No issues found in unused-imports check.. Please refer the workflow run |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Note that the smoketest |
Thank you - issue fixed in commit 9212b40 |
Should be added as runtime option similar to "terminal monitor" known from other vendors.
Move "global preserve-fqdn" one CLI level up, as it relates to all logging targets (console, global and remote).
The previously "global" options actually were only relevant for the local logging to /var/log/messages.
This is a feature that worked decades ago when logs were small and reviewed by a human, it fails badly on high volume logs processed by tools. https://www.rsyslog.com/doc/configuration/action/rsconf1_repeatedmsgreduction.html
Rsyslog supports individual VRFs per omfwd remote entry - so we should support this, too.
Some systemd services are re-used over multiple configuration files. Keep a single source of the real systemd names and only reference them by dictionary keys.
CI integration 👍 passed! Details
|
Change summary
We are still using the legacy config format for rsyslog in https://github.com/vyos/vyos-1x/blob/bb4611544ff73a979f927a7a1c8ea3dd1c56fb48/data/templates/rsyslog/rsyslog.conf.j2
It has been superseded by a new format:
https://www.rsyslog.com/doc/configuration/converting_to_new_format.html
There are some associated issues. For example, we use
$markMessagePeriod
forset system syslog global marker interval
, which sends mark messages unconditionally. New rsyslog versions support sending mark messages only if there are no real messages, the old directive is now listed as obsolete (https://www.rsyslog.com/doc/configuration/input_directives/rsconf1_markmessageperiod.html) and its replacement seems to be only available in the advanced format.file
CLI option to log to dedicated files.user
CLI option to always log to user terminal - should be an op-mode command insteadhost <ipv4|ipv6|fqdn>
->remote <ipv4|ipv6|fqdn>
remote source-address <ipv4|ipv6|fqdn>
remote vrf <name>
global preserve-fqdn
->preserve-fqdn
- move up one CLI levelglobal marker interval
->marker interval
- move up one CLI levelglobal
->local
as every facility configured under global is actually logged locally to/var/log/messages
Types of changes
Related Task(s)
Related PR(s)
How to test / Smoketest result
Checklist: