Collect information on how the new DS analyzer was introduced
Problem statement
We would like to know how users are introducing the new DS analyzer. Currently there are 3 ways of introducing it:
- latest template
- v2 template
- Beta component
Proposal
We could introduce an internal env var which could contain information like the following:
- template::latest
- template::v2
- template::stable
- component:v1.1.0
Then we could track these values with the use of an event
{
"event": "collect_ds_analyzer_scan_ci_integration_metrics_from_pipeline",
// Columns (join, filter, fast)
"property": "scan_uuid", // join: Allows joining
"label": "<INTERNAL_DS_ANALYZER_CI_INTEGRATION>" // fast: Config environment variable value
}
Implementation plan
-
Extend latest and v2 template with INTERNAL_DS_ANALYZER_CI_INTEGRATIONenv var -
Extend Beta component with INTERNAL_DS_ANALYZER_CI_INTEGRATION -
Create an event for collect_ds_analyzer_scan_ci_source_metrics_from_pipelinein GitLab -
Create an event for collect_ds_analyzer_scan_ci_source_metrics_from_pipelinein event registry -
Update the DS analyzer to send the event
Edited by Nick Ilieskou