Kryesh@lemmy.worldOPtoSelfhosted@lemmy.world•Building my own log aggregation and search serverEnglish
1·
5 days agoThanks! definitely aiming for a stupid easy installation/management for the app itself; but in my experience getting a wide range of supported log sources is no small feat. I’ve been using fluentbit to handle collection from different sources and using the following has been working well for me:
- docker ‘journald’ log driver
- fluentbit ‘systemd’ input
- fluentbit ‘http’ output like the one in the readme
with that setup you can search for container logs by name which works great with compose:
or process logs from an nginx container like this to see traffic from external hosts:
I’ll add a more complete example to the docs, but if you look in the repo there’s a complete example for receiving and ingesting syslog that you can run with just “docker compose up”
I’m currently using the fluentbit http output plugin, fluentbit can act as an otel collector with an input plugin which could then be routed to the http output plugin. Long term I’ll probably look at adding it but there’s other features that take priority in the app itself such as scheduled searching and notifications/alerting