Simple way to centralize my server logs?

• tailon

  2 22 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

• Logstash

  5 13,999 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

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Fluentd

  25 12,531 8.0 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

• vector

  96 16,427 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

• xsrv

  24 288 9.7 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.

• frontail

  2 1,791 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.

• gotty

  17 2,059 4.5 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.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• serilog-sinks-seq

  11 210 6.1 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