[EPIC] Plutono Replacement: Evaluation of Perses

[ibakshay]

Context

Currently, We are using Plutono a fork of Grafana for all our dashboards and visualisations. However, Plutono is in maintenance-only mode, making it a non-viable long-term solution. We need to identify and adopt a suitable alternative that fulfils our requirements.

Requirements for a New Tool

• Open-source with an Apache 2.0 license
• Ability to connect to Prometheus and Thanos data sources
• Support for creating custom dashboards
• Management of dashboards using a Dashboard as Code approach

The alternative tool that we are considering is perses. Perses which is a CNCF sandbox project shows strong potential as a viable replacement for Grafana/Plutono. Perses is currently in the early stages of active development. 

This tools satisfies most of our requirements. So, we have to evaluate this tool by doing a POC. The POC should cover the following:

Acceptance Criteria:

• Test perses in our test sandbox environment.
  • [perses] Evaluate upstream helm-charts for the set up #418
  • [perses] check feasibility of perses-operator #419
  • [perses] Connect perses to our Prometheus data sources. #420
•  dashboards
  • create a custom dashboard using perses.
  • investigate migration tool to convert existing dashboards #480
    • Migration tooling provided by Perses for latest Grafana. Dashboards created with Plutono, which is based on older Grafana version, doesn’t work out of the box. Manual work required.
•  Try out the Perses CLI
• POC: Greenhouse dashboard for self-monitoring to avoid migration.
• community work
  • report issues upstream
  • critical issues might be tackled with upstream contribution

Additional context.

No response

Reference Issues

No response