[systemd-devel] Direct systemd-journald event-logs tranmssion to Zabbix\Cacti

[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. If you
want syslog, use syslog, but systemd will not natively output syslog.

> JSON, HTTP(S) etc. -- that's great, but HTTP(S) is actually used
> for web-surfing. And it often procced with port-redirections (on Squid
> for example), shaping the speed depending on web-content and so on.

Well, HTTP is kinda the basic building block of most modern protocols,
because it can easily go through proxies. It's certainly not a thing
exclusively for web surfing... You can print via HTTP, you can
checkout your git tree, there's SOAP and REST APIs, and whatnot. It's
simply how you design internert protocols these days that fit into the
concept of HTTP requests/responses. And logging certainly does.

> "It'd would be easy for external services to simply speak HTTP and get
> the data out of there." (с) - yes, but there're many factors (traffic
> shaping, other firewall ruling etc.) that potentially can affect on
> systemd-journald logs transmission. So, the systemd-journald's dedicated
> documented transports (open and secure) will be good idea.

The http-based protocol journald-gatewayd and related tools speak is
pretty well documented.

Again, we won't support BSD syslog natively. If you want syslog,
install a syslog implementation, there are many to choose from. Or use
the HTTP stuff we do, but don't expect us to natively to syslog in systemd.

Lennart

-- 
Lennart Poettering, Red Hat