← Directory

p10logs

Lightweight, persistent, multi-cluster Kubernetes pod-log aggregation.

  • Tools & Utilities
Lightweight, persistent, multi-cluster Kubernetes pod-log aggregation. Logs only, no metrics.

Platform availability

Available on 1 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm

Also on GitHub

Health score

41/100 Fair

Maintained
75last commit 1 day ago
Popular
102 GitHub stars
Easy to install
101 install platform
Light to run
No data

Based on 3 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today

GitHub stars
2
Open issues
0
Last commit
2026-10-07
Latest release
v1.1.4
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (p10node/p10logs)

Resources & Compatibility

Requirements not published yet.

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

Does p10logs collect metrics or traces, or only logs?

It is a logs-only system. It does not require a metrics pipeline, Prometheus, Grafana, Elasticsearch, or an object store.

What happens if the hub process is killed?

The hub stores logs on a persistent volume. A kill -9 hub recovery with WAL replay is covered by the test suite.

Can a separate Kubernetes cluster send logs to a central p10logs hub?

Yes, a multi-cluster test covers a spoke cluster pushing logs over the network to a hub cluster. It also covers a hub outage with spool and drain.

Is the p10logs API stable for custom tooling?

The project is at v1.1. Its formats and /api/v1 API are frozen since 1.0.

Can access be scoped per cluster or viewer role?

The end-to-end tests cover per-cluster tokens, viewer roles, federation, and token scoping.

Answers sourced from github.com

Community

No community discussions collected yet.