On 2021-04-24 22:50, li...@mailbox.org wrote:
Do you have any best / bad practices at hand regarding OpenBSD and
optionally the syslogd / tools it ships with?
The main issue with remote logging is that your log messages could be
lost
when destination is unreachable.
Default syslogd(8) shipped with OpenBSD supports remote log destinations
with mutual TLS authentication, but man page is somewhat silent about
reliability. You can pipe all log entries to an external application
tho,
and leveraging whatever log dispatch mechanism you find suitable for
your case.
You can also find syslog-ng in ports which have more bells and
whistles, such as SQL support and whatnot. The important part would
be to enable disk buffering for outgoing log entries in case destination
server is unreachable. Syslog-ng has such option:
https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/administration-guide/disk-buffer
Cheers,
Chris
