backend: switch syslog implementations #19

New issue

Closed

opened 2022-07-21 00:03:49 +00:00 by toast · 3 comments

toast commented

2022-07-21 00:03:49 +00:00

Owner

https://www.npmjs.com/package/syslog-pro is absolutely horrifying and explains why it's unusable at large.
It's only used in packages/backend/src/services/logger.ts so should be easy to do minus config stuff.

https://www.npmjs.com/package/syslog-pro is absolutely horrifying and explains why it's unusable at large. It's only used in `packages/backend/src/services/logger.ts` so should be easy to do minus config stuff.

image.png

37 KiB

toast self-assigned this 2022-07-21 00:03:49 +00:00

toast added this to the (deleted) project 2022-07-21 00:03:49 +00:00

norm referenced this issue from a commit

2022-08-28 14:46:46 +00:00

add FetchLike (#19)

norm commented

2022-09-04 02:50:49 +00:00

Owner

Kinda wonder if we really even need to use syslog these days. I imagine most will just let the server output to stdout/stderr and have that captured by systemd or some other logging daemon.

Kinda wonder if we really even need to use syslog these days. I imagine most will just let the server output to `stdout`/`stderr` and have that captured by systemd or some other logging daemon.

Michcio commented

2022-09-04 08:26:43 +00:00

Contributor

How does that work on OpenRC systems like Alpine? (And more importantly do we have any users running on that?)

toast commented

2022-09-04 11:20:36 +00:00

Author

Owner

How does that work on OpenRC systems like Alpine?

It works just fine, use output_log or output_logger with rotations.

And more importantly do we have any users running on that?

The thing with the current syslog implementation is that it's remote-only (and not many things beyond rsyslog and syslog-ng (both of which must be explicitly configured to do that) actually listen on those ports).
If we were to replace it, I'd like to use syslog(3).

> How does that work on OpenRC systems like Alpine? It works just fine, use `output_log` or `output_logger` with rotations. > And more importantly do we have any users running on that? The thing with the current syslog implementation is that it's remote-only (and not many things beyond rsyslog and syslog-ng (both of which must be explicitly configured to do that) actually listen on those ports). If we were to replace it, I'd like to use `syslog(3)`.