https://www.pistack.xyz/tags/logging/Recent content in Logging on Pi StackHugoen-usMon, 20 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/2026-04-20-openobserve-vs-quickwit-vs-siglens-self-hosted-observability-guide-2026/Mon, 20 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/2026-04-20-openobserve-vs-quickwit-vs-siglens-self-hosted-observability-guide-2026/<p>When your infrastructure grows beyond a handful of servers, log aggregation and observability stop being nice-to-have features and become critical operational requirements. The traditional answer — the ELK stack (Elasticsearch, Logstash, Kibana) or a SaaS platform like Datadog — comes with significant cost, com<a href="https://www.plex.tv/">plex</a>ity, and data sovereignty trade-offs.</p>https://www.pistack.xyz/posts/2026-04-18-rsyslog-vs-syslog-ng-vs-vector-self-hosted-syslog-log-aggregation-guide-2026/Sat, 18 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/2026-04-18-rsyslog-vs-syslog-ng-vs-vector-self-hosted-syslog-log-aggregation-guide-2026/<p>Every server, container, and network device generates logs. Without a centralized collection strategy, troubleshooting means SSH-ing into individual machines, tailing files, and hoping you catch the error before it scrolls off screen. A self-hosted syslog aggregation pipeline solves this by collecting logs from all your infrastructure into a single searchable location — without sending sensitive data to a third-party cloud service.</p>https://www.pistack.xyz/posts/self-hosted-log-management-loki-graylog-opensearch/Sun, 12 Apr 2026 00:00:00 +0000https://www.pistack.xyz/posts/self-hosted-log-management-loki-graylog-opensearch/<p>If you run more than a handful of self-hosted services, tracking down errors across scattered log files becomes a nightmare. SSH into five different containers, <code>grep</code> through rotating files, and still miss the critical stack trace that explains why your reverse proxy dropped traffic at 3 AM.</p>