Am 01.12.2015 um 22:35 schrieb oliver:
On Tue, Dec 1, 2015 at 4:20 PM, J.C. Cleaver <user-87556346d4af@xymon.invalid> wrote:
The simplest way to integrate would be to alter the xymonclient.sh code to
have journalctl dump log contents using the *cursor or --since options to
a separate file, which logfetch reads and handles like a "normal" log file
to scan, which we rename or symlink around as needed. This has the
advantage of allowing use of all the existing client-local.cfg rules
regarding triggers and ignoring. We then save the cursor and start there
for next time.
journald.conf supports the ForwardToSyslog option
============================
Control whether log messages received by the journal daemon shall be
forwarded to a traditional syslog daemon, to the kernel log buffer
(kmsg), to the system console, or sent as wall messages to all
logged-in users.
============================
This i widly known , but i think that is/will be not default in many distros
so having native journalctl log monitoring will be very usefull in any case
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein