KCP KEB/Managed Runtime business metrics + Grafana Dashboard

[PK85]

Description

We currently have the General / KCP / Kyma Environment Broker Grafana dashboard which shows some general information about the number of Kyma instances, provisioning and upgrade status per plan, resource consumption, and Golang metrics. This is quite a big view and adding further information could be cumbersome.

I'd like to have a new Dashboard General / KCP / Kyma Environment Broker - Business Metrics with extended Runtime Business Metrics.

Reason

This new view will provide detailed information about Kyma usage.

AC

• Kyma team GAs Costs for Development - details
• Number of Kyma instances per plan (aws, gcp, trial, free, etc)
• Number of Kyma trial clusters created/suspended in the given month
• Number of Kyma instances created by user @sap.com
• Number of Kyma instances with empty user
• Number of Kyma instances with custom OIDC
• Number of Kyma instances created per year (current), for example:
  • 2020 - 30
  • 2021 - 100
  • 2022 - 88
  • etc
• Number of Kyma instances per subAccountRegion e.g. "cf-us10"
• Number of Kyma instances per latestOperation state (SUM of that should equal all number of Kyma instances)e.g.
  • provisioning - succeeded / failed / in progress
  • deprovisioning - succeeded / failed / in progress
  • upgrading Kyma - succeeded / failed / in progress
  • upgrading Cluster - succeeded / failed / in progress
  • suspended - succeeded / failed / in progress
  • deprovisionIncomplete
• Number of Kyma instances where shoot ID does not exist in the Gardener project
  • Generally, we'd like to see SKRs that are in final state e.g. succeeded and have no shoots
  • Maybe we can reuse existing metrics about shoot existence
• Metrics from our jobs
  • trial-cleanup-job.yaml
  • subscription-cleanup-job.yaml
  • subaccount-cleanup-job.yaml
  • deprovision-retrigger-job.yaml
  • keb-db-job.yaml

To be discussed

• For some of the above metrics maybe we will need to have a job that will calculate metrics accordingly.

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.