[systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti
Lennart Poettering
lennart at poettering.net
Tue Oct 27 05:24:49 PDT 2015
On Mon, 26.10.15 23:43, Mikhail Kasimov (mikhail.kasimov at gmail.com) wrote:
> 26.10.2015 17:35, Lennart Poettering пишет:
> > On Mon, 26.10.15 15:54, Mikhail Kasimov (mikhail.kasimov at gmail.com) wrote:
> >
> >> Hello Lennart! The main question is not about why rsyslog is
> >> better/worst compared to systemd-journald. The main question is how to
> >> transmit journald event-log to centralized log-server (Zabbix\Cacti\so
> >> on) directly, without any additional assistant layers (rsyslog in this
> >> case).
> >
> > This is not supported, and I doubt we will ever support that.
>
> Why not? Can you declare in /etc/services that, for example, UDP 19531
> is systemd-journald port (it's not native rsyslog supporting - it's only
> the same way of it to have a logically finished log-system, which has
> internal and external mechanisms of event-log transmission), and TCP
> 19531 and TCP 19532 are 'systemd-internal-log-transmission'?
Because BSD syslog is not a well-designed or well-specified protocol,
and there's nothing stopping you from doing this, but with software
outside of systemd.
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list