perses/perses — The CNCF sandbox for observability visualisation.

Description and use

**Summary**
Perses ( github.com/perses/perses ) is a CNCF‑sandbox project that provides a unified, web‑based UI for visualising observability data from Prometheus, Tempo, Loki and Pyroscope, with more sources planned. It lets teams turn raw metrics, traces, logs and profiling data into searchable dashboards and automated pipelines, simplifying analytics, reporting and incident‑response workflows.

**Value**
By consolidating multiple observability back‑ends under a single, extensible front‑end, Perses eliminates the need for separate Grafana or custom tooling stacks, reducing operational overhead and enabling faster, cross‑domain insights. Its Go‑centric architecture and declarative pipeline definitions make it easy to embed in CI/CD or data‑processing workflows, turning raw telemetry into actionable, queryable artifacts.

**Practical adoption path**

1. **Proof‑of‑concept** – clone the repo, run the Docker compose example, and point it at an existing Prometheus/Loki instance to validate dashboard rendering.
2. **Integration** – add Perses as a side‑car service in your observability stack, configure the data‑source connectors via the provided YAML, and create a minimal set of dashboards that mirror your current Grafana views.
3. **Pipeline rollout** – progressively replace ad‑hoc queries with Perses‑defined pipelines (e.g., automated alert generation or report export) and iterate on the UI configuration.

**Production readiness**
Perses scores high on readiness: recent commits (last update 2026‑05‑11), 2 k+ stars, active forks, and strong CNCF sandbox endorsement indicate a healthy community and ongoing maintenance. While the license and security posture still require a final audit, the project’s activity level, Go codebase, and existing adoption in several pilot environments make it a solid candidate for a serious production pilot.

Problem

perses/perses helps convert raw data into searchable, analyzable, or automated pipelines.

Outcome

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.

Workflow

• organize analytics pipelines
• process datasets
• improve reporting workflows

Evidence

The CNCF sandbox for observability visualisation. Already supports Prometheus, Tempo, Loki and Pyroscope - more data sources to come!

Source