Epic Goal

• Enable OpenShift pipelines to send usage metrics

Why is this important?

• To baseline and improve metrics that are important for the success of the product

Scenarios/Metrics

1. number of operator installs - available - comment by @koustav- you have to run some promquery for "Low number of non-running instance", but possible.
   1. Low number of non-running instance
   2. Ratio between installed supported version versus non-supported (channel + version)
2. tracking new installs daily, weekly, monthly (without stickiness)
   1. metric: to gauge “customer acquisition rate" - available as per @kbaig
3. tracking stickiness over time after installation (days, weeks, months) - This should also be available - kbaig.
4. No of customers 
   1. Feature/component Adoption by customers 
5. No of unique pipeline runs
   1. Shows customers increased adoption of pipelines
6. track the number of customers using a specific component:
   1. Ratio of component specific PipelineRuns vs all PipelineRuns

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

https://docs.google.com/document/d/1FwAlrKz8afYj83kxcsMhEqzdETYDgnosbSKu_JPyfT8/edit# 

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment
• Once Metrics are added in the respective components as well as Operator next step is to coordinate with Telemetry team via https://issues.redhat.com/browse/MON-2975