# p10logs

p10logs is a self-hosted tools & utilities app. Lightweight, persistent, multi-cluster Kubernetes pod-log aggregation. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/6870/p10logs

## Description

Lightweight, persistent, multi-cluster Kubernetes pod-log aggregation. Logs only, no metrics.

## Platform availability

Available on 1 of 6 install platforms: Helm.

## Health score

41/100 (Fair), based on 3 of 4 factors.
- Maintained: 75 (last commit 1 day ago)
- Popular: 10 (2 GitHub stars)
- Easy to install: 10 (1 install platform)

## Links

- Kubernetes (Helm): https://artifacthub.io/packages/helm/p10logs/p10logs
- GitHub: https://github.com/p10node/p10logs
- Documentation: https://p10node.github.io/p10logs/
- Official website: https://p10node.github.io/p10logs/

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6870/p10logs), the self-hosted and open-source app directory.