iopsys-feed/logmngr/files
Mohd Husaam Mehdi 9e69ed7bc0 logmngr: use separate fluent-bit instances for main and user conf
So the philosophy here is that there will be one main fluent-bit
instance, which will read from /dev/kmsg and /dev/log and write to
/var/log/messages.
This is done to reduce the chance of introducing errors in config
and making sure that var/log/messages is always populated because
logread depends on it.
For example, an unavailable URL for a udp based syslog output plugin
can cause fluent-bit to exit entirely.
The other fluent-bit instance uses a different "user" config file.
Which will handle log_file, log_remote and included configs. It has
a single hard coded input tail plugin which reads from
/var/log/messages.
Any filter that is applied will act on the main config and thus,
only filtered logs will be available to both fluent-bit instances.
2026-01-22 21:20:24 +05:30
..
etc logmngr: use separate fluent-bit instances for main and user conf 2026-01-22 21:20:24 +05:30
lib/logmngr logmngr: use separate fluent-bit instances for main and user conf 2026-01-22 21:20:24 +05:30
logread logmngr: multiple fixes 2025-03-24 18:37:58 +05:30