Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-460

Add new helm Dimension to Deployment metric

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Helm

      Owner: Architect:

      David Peraza

      Story (Required)

      As an OpenShift Helm developer, I will like to know how many OpenShift Deployment resources are created via helm chart so that I can count Deployments in our fleet that come from helm.

      Background (Required)

      Today we are able to set Chart install/update/delete metrics from ODC. This will give us an idea of adoption during the onboarding phase of the application lifecycle. However, is not the full picture. We tried to complement this with OpenShift helm chart downloads, but that is also incomplete as it only include chart that we published in our certification program. To have a better idea of adoption we need to have another metric that represents both UI metrics and CLI metrics.
      The Idea is to add a new dimension to existing metrics for a common resource encapsulated with helm chart. Deployments are a good candidate. We can search for the deployments in the observe section in odc using kube_pod_labels

      {label_app_kubernetes_io_managed_by="Helm"}

      .

      Glossary

      NA

      Out of scope

      Creating new metric

      In Scope

      NA

      Approach(Required)

      There is already a metric for Deployment. Need to add example here. We need to find how that metric is added in OpenShift and include a metric dimension for helm-owned.

      Demo requirements(Required)

      A good demo will show deployment metrics in our fleet and allow us to filter dashboard with helm-owned dimension.

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      Can show in thanos and grafana how many Deployments are helm owned compare to total deployments.
      No docs needed

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      v

      Legend

      Unknown

      Verified

      Unsatisfied

            Unassigned Unassigned
            dperaza@redhat.com David Peraza
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: