Migrate monitoring dashboards to Perses

[scholzj]

Currently, our example dashboards are based on Grafana. However, during the license changes (move to AGPL) that not firendly to all users, we always aim to support the older Grafana versions with less restrictive license. That is bringing issues as Grafana evolves.

We should consider moving the dashboards to Perses as ASL2.0 licensed project that is part of CNCF.

As part of this issue, we should:

• Investigate how much work effort it is to move to Perses. Do the migration tools work out of the box? Does it need a lot of changes and fine-tuning to get working dashboards?
• What to do with the Grafana dashboards? Remove them? Keep them, but not update them? Move them to some contrib repo for the community to maintain?
• What to do with the Helm embeddings (The Grafana dashboards are bundled in the Helm Chart)?

[im-konge]

The migration guide looks like it should work - https://perses.dev/perses/docs/migration/ - but we would need to try with our dashboards.

[ppatierno]

+1 from me. It would also show another perfect integration of Strimzi within the CNCF landscape.
Of course, as part of the migration, the documentation will need to be updated as well providing some steps or links to refer to for installing Perses instead of Grafana.

[im-konge]

Marking this as triaged based on the rules of asynchronous issue triage. This needs investigation and answers to the points Jakub mentioned in the issue description - that should be covered by the proposal.