Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-2913

consultancy: Add new helm Dimension to Deployment metric

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • NEW
    • NEW
    • 0

      • Describe the issue, question or problem you have.
        • We are currently making use of insights operator to gather the prometheus metrics related to Helm install/uninstall and upgrades. The problem with this approach is that we are restricted to get insights from Helm ODC rest api. We would also like to gather the information related to Helm usage from cli.The idea which are looking to exploit is the presence of kube_deployment_labels in kube state metric swhich are currently monitored by cluster monitoring operator. We would like to know if this gauge metric can be used to achieve the goal or can we add an attribute to this metric which can act as a differentiator for deployments created and not created by Helm.
      • Is your team currently blocked?
      • Describe the business criticality and importance of this request.
        • This request is critical to us as we would like to know the adoption of Helm both from cli and openshift console. We are covered by ui but need to get complete Helm usage from cli as well.
      • What is your explicit request to the team?
        • We would like to understand the path to be taken to get the information of deployments created and not created by Helm. We have done a few investigations which can be tracked by https://issues.redhat.com/browse/HELM-470.

            jfajersk@redhat.com Jan Fajerski
            kmamgain@redhat.com Kartikey Mamgain
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: