Add distinct user count of secure stage items to usage ping
requested to merge update-secure-usage-ping-to-be-able-to-determine-number-of-jobs-by-user into master
What does this MR do?
Add new secure stage fields to the usage ping
name of these new fields(explain from database-lab):
- user_container_scanning_jobs - https://explain.depesz.com/s/ynqN
- user_dast_jobs - https://explain.depesz.com/s/dOa
- user_dependency_scanning_jobs - https://explain.depesz.com/s/aGk8
- user_license_management_jobs - https://explain.depesz.com/s/m8s
- user_license_scanning_jobs - https://explain.depesz.com/s/h8pj
- user_sast_jobs - https://explain.depesz.com/s/9jqd
These fields will be the distinct users to have triggered these items
Closely follows gitlab-org/secure/general#63 (comment 295633948) as a spec
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Jan Provaznik