Summary

Review vector's open issue related to implementing forwarding to syslog and determine:

• the state of affairs
• is there a place for us to contribute

Acceptance Criteria

• Summarize syslog findings
• Create JIRA cards for follow-on work

Notes

• There's indeed no syslog sink in the vector codebase There was a PR https://github.com/vectordotdev/vector/pull/7106 , but it was not merged due to the foundation code having been removed from under it.

• There is a syslog source, built on top of a syslog parser crate, which also includes a syslog serializer, which can be used in the new syslog sink

• There're traits and impls ("base classes") for different types of sinks. The one most closely fitting what the syslog sink needs is SocketSink.
• The https://issues.redhat.com/browse/LOG-2914 epic carries the follow-up stories for this spike.