• Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • OADP 1.0.0
    • None
    • None
    • False
    • False
    • Not Required
    • OADP Sprint 204, OADP Sprint 215, OADP Sprint 216
    • 3
    • 0
    • 0
    • Untriaged
    • None

      We will want to establish some basic metrics we can report back to Telemetry.

      Let's consider:

      • Operator installs
      • Backups, created, success, error
      • Restores created, success, error

       

      Below is some background info from MTC when we added Telemetry support that may help

       

      See:  https://github.com/konveyor/metrics-queries/blob/master/README.md

       

      Design/Development info:

      OpenShift Monitoring Integration Guide

      Sending metrics via telemetry

      Monitoring integration with OLM operators

      https://www.openshift.com/blog/observability-superpower-correlation

       

      Source Code:

      https://github.com/konveyor/mig-controller/blob/master/pkg/controller/migmigration/metrics.go

            [OADP-22] Send Telemetry metrics on OADP

            Shubham Pampattiwar added a comment - Related PRs: https://github.com/openshift/oadp-operator/pull/410 https://github.com/openshift/oadp-operator/pull/537 https://github.com/openshift/oadp-operator/pull/579 https://github.com/openshift/cluster-monitoring-operator/pull/1536

            Also perhaps a useful reference: a usage guide for the metrics implemented in mig-controller / mig-operator: https://github.com/konveyor/mig-operator/blob/master/docs/usage/Metrics.md

            Derek Whatley (Inactive) added a comment - Also perhaps a useful reference: a usage guide for the metrics implemented in mig-controller / mig-operator:  https://github.com/konveyor/mig-operator/blob/master/docs/usage/Metrics.md

            Derek Whatley (Inactive) added a comment - - edited

            rhn-engineering-dymurray spampatt@redhat.com IIRC, this PR was the last piece of the puzzle for getting metrics enabled and sent back to Telemeter.

            The process has perhaps changed, so you'll want to refer to the docs John provided above under Design/Development info for most up to date info, but the PR I'm linking here has links to all PRs that were required : https://github.com/openshift/telemeter/pull/298

            • Adding metrics to mig-controller
            • Adding servicemonitor to mig-operator
            • Getting approval from Clayton on the cardinality of our metric (since we need to be mindful of collection budget shared with other operators)
            • Adding collection entry for our metric to telemeter

            Derek Whatley (Inactive) added a comment - - edited rhn-engineering-dymurray spampatt@redhat.com  IIRC, this PR was the last piece of the puzzle for getting metrics enabled and sent back to Telemeter. The process has perhaps changed, so you'll want to refer to the docs John provided above under  Design/Development info for most up to date info, but the PR I'm linking here has links to all PRs that were required :  https://github.com/openshift/telemeter/pull/298 Adding metrics to mig-controller Adding servicemonitor to mig-operator Getting approval from Clayton on the cardinality of our metric (since we need to be mindful of collection budget shared with other operators) Adding collection entry for our metric to telemeter

              spampatt@redhat.com Shubham Pampattiwar
              jmatthews John Matthews
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: