Track internal events for Gitlab CLI actions
What does this MR do and why?
Enables tracking usage of the GitLab CLI for gitlab.com (and self-managed instances with event tracking on).
Snowplow event tracking doesn't need to be blocked by service ping metric configuration, so this MR pulls the event definition out of !190595 (merged) to let that piece get merged a little quicker.
References
- Add glab CLI event definitions (!190595 - merged)
- Add a redis hash counter (for future use in tra... (!185183 - merged)
Testing
GitLab CLI events will be triggered through the REST API usage_data/track_events.
This event can be triggered through the rails console with:
Gitlab::InternalEvents.track_event('gitlab_cli_command_used', project: Project.first, user: User.first, additional_properties: { label: 'mr', property: 'view', command_and_subcommand: 'mr view' })MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.