Backend: Implement Pipeline Execution Feature Tracking in Service Ping

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

We should have better tracking for usage of some key features to make better data informed product decisions within Pipeline Execution. To do this we should capture unique user usage for more features than our Performance Indicator of users triggering pipelines

This issue may get promoted to an epic with issues for each metric.

The initial metrics to track would be:

• Count of users who add an MR to a merge train
• Count of users who trigger a pipeline with child pipelines
• Count of users who trigger a pipeline that has an external repository