Support for syslog format RFC5424

[durd]

Enhancement summary

RFC5424 is the current RFC for the syslog protocol. Although most of my customers aren't using RFC5424 directly, I have a few customers that require RFC5424 formatting. This feature request would allow users to configure and select RFC5424 as a logging format.
logging format rfc5424 is the command in EOS 4.30.3M.

AVD component impacted would be eos_cli_config_gen as that is where config for logging is done.

Which component of AVD is impacted

eos_cli_config_gen

Use case example

I don't have much experience with SIEM products, mainly logstash, but from what I hear they are fickle in what format they can receive syslog messages in. Fickle in the way that they can't easily be set up to accept both RFC5424 and RFC3126. Therefore and since RFC5424 obsoletes RFC3164 more and more SIEM systems default to RFC5424.

Describe the solution you would like

The solution I'd like is for eos_cli_config_gen to support the configuration of logging format rfc5424. Looking at the logging.j2 template this change seems straight forward as other logging format options are already supported.
Note that I haven't looked at creating tests for this, I also understand that there needs to be documentation created.

Describe alternatives you have considered

A direct alternative would be to create a custom template to attach to eos_cli_config_gen with suitable YAML.

Additional context

No response

Contributing Guide

• I agree to follow this project's Code of Conduct

[durd]

I'm sorry, I saw that there was a mailing list (discussion board?) and this should have been discussed there in beforehand, but I'm not sure why it didn't register with me.

[gmuloc]

Hi @durd - thanks for opening the issue sounds like you are missing the logging format rfc5424 option in eos_cli_config_gen

host3(config)#show cli commands | grep "logging format"
[no|default] logging format hostname fqdn | ipv4
[no|default] logging format rfc5424
[no|default] logging format sequence-numbers
host3(config)#

Indeed today this is not supported so this is the right place to open an issue!

To add this to eos_cli_config_gen, the following steps are required in eos_cli_config_gen:

1. update schema fragment for logging to add the key
2. update eos and documentation templates
3. add some test in molecule

some more info on this issue #3286

If you feel like you want to try to take this upon you let us know

[durd]

I think I'm up for the challenge!
As I mentioned, other logging format ... options are available that I can reference against so I'm positive I can work out a good PR.

[gmuloc]

Ok! let us know if you need any help!