dedicated `tracing-syslog` crate

[mainrs]

Feature Request

Motivation

On systems without systemd, the tracing-journald crate won't work. For those systems, a dedicated tracing-syslog crate would be beneficial.

Proposal

This feature should be implemented inside its own crate under the same workspace.

Alternatives

In theory, it should be possible to enable the tracing-log interop in combination with syslog. However, in my opinion, this is more of a dirty workaround 😄.

Misc

Work has not been started on any fork.

[max-heller]

After using the tracing/log+syslog crate combination for a while and being frustrated with the lack of configurability and general interfacing with tracing, I decided to look into a syslog-backed Subscriber. I have something working that handles events (but ignores spans completely for now) that I'll be making a PR for soon. @hawkw should I branch off of master or 0.1.x? Things seem to be rather in flux right now

[max-heller]

As discussed in #1137, tracing-syslog won't be getting added to the tracing monorepo, but I've moved the code to max-heller/tracing-syslog. Try it out and let me know if it works for your use-case, and I can publish it to crates.io!

[max-heller]

Finally published the crate as syslog-tracing. I was trying to get ownership of the name-squat tracing-syslog but couldn't get in contact with the owner.