Simple way to centralize my server logs?

1. tailon

   1 2 29 3.5 Go

   Webapp for looking at and searching through files and streams. Fork of https://github.com/gvalkov/tailon

   

   I know about tailon, but not sure if it's exactly what you're looking for

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. Logstash

   2 5 14,535 9.6 Java

   Logstash - transport and process your logs, events, or other data

   

   There are probably too many to chose from. Logstash, Promtail, Vector, Filebeat, FluentD, Logagent and probably many more

4. Fluentd

   3 29 13,194 9.4 Ruby

   Fluentd: Unified Logging Layer (project under CNCF)

   

   There are probably too many to chose from. Logstash, Promtail, Vector, Filebeat, FluentD, Logagent and probably many more

5. vector

   4 114 19,759 9.9 Rust

   A high-performance observability data pipeline.

   

   There are probably too many to chose from. Logstash, Promtail, Vector, Filebeat, FluentD, Logagent and probably many more

6. xsrv

   5 24 362 9.3 Jinja

   [mirror] Install and manage self-hosted services/applications, on your own server(s) - ansible collection and utilities

   

   I use rsyslog for that since it's the default in Debian. Configuring forwarding is very simple, a single file in /etc/rsyslog.d/forwarding.conf [1]. Note that this setup uses TLS to encrypt messages so you need to create the relevant certificates (I use self-signed certs). Unencrypted TCP or UDP is simpler, but less secure.

7. frontail

   6 2 1,831 0.0 JavaScript

   📝 streaming logs to the browser. Sponsored by https://cloudash.dev

   

   Honestly graylog/loki is only worth it if you want to have automatic processing/stats generation/graphing and complex log management rules. If you just want to read logs in a web interface I suggest either frontail (very basic, a bit too much for my taste) or lnav (I use this 99% of the time, over SSH) + gotty to access a terminal/lnav from a web browser - be careful to secure it properly as it basically gives shell access to your server.

8. gotty

   7 17 2,265 5.1 Go

   Share your terminal as a web application (by sorenisanerd)

   

   Honestly graylog/loki is only worth it if you want to have automatic processing/stats generation/graphing and complex log management rules. If you just want to read logs in a web interface I suggest either frontail (very basic, a bit too much for my taste) or lnav (I use this 99% of the time, over SSH) + gotty to access a terminal/lnav from a web browser - be careful to secure it properly as it basically gives shell access to your server.

9. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

10. serilog-sinks-seq

    8 14 251 7.5 C#

    A Serilog sink that writes events to the Seq structured log server

    

    I know I’m a little late to the game, but check out Seq. If you use Docker, you can deploy Seq and Seq-input-gelf Docker containers, set gelf as the default logging driver in your daemon.json, and point it at you Seq instance. That’s pretty much it. Seq also accepts a bunch of other log inputs, like Greylog, for things that don’t run in Docker.

Suggest a related project