Create event-based metric for CI builds
Problem
Database-based metrics for CI builds create a big load on the database of customers during Service Ping calculation. This goes up to the point that they disable the service ping. See #350971.
A metric for this table is used as health score for customers to evaluate their usage.
This leads to multiple more problems:
- bad experience for customers having to disable the service ping
- no way for CSM to evaluate the successfulness of those customers with regards not only to CI builds but in general with the lack of a Service Ping
Desired Outcome
A less resource-intensive replacement for the following metrics is in place so that they can be shut off down the line:
counts.ci_builds
counts_monthly.ci_builds
usage_activity_by_stage_monthly.verify.ci_builds
usage_activity_by_stage.verify.ci_builds
Proposed solution
Create an event whenever a new entry that would be counted by a CI builds metric is created and use Internal Event tracking to configure appropriate replacement metrics for the existinc CI build metrics.
Pipeline execution team involvement
Guide the placement of the implementation by groupanalytics instrumentation.
Further Information
The explanation in this video outlines why it is important to deliver these new metric. We can only shut off the DB based metrics after the Event-based ones have been established for some time.