Track event when job token is authorized for a project with disabled scope

What does this MR do and why?

Addresses item 8 from #478522 (closed):

8. Unique number of projects receiving authentications while having disabled scope and distinguish between same-project vs cross-project authentications - helps distinguish how many projects use CI_JOB_TOKEN but there is no need to populate the allowlist (same project) vs the cross-project where we need to populate the allowlist. The first numbers will also help calculate the number of projects not impacted at all (inactive or without inbound CI_JOB_TOKEN)

Also updated the module Gitlab::InternalEventsTracking to make track_internal_event usable inside class methods.

changed milestone to %Next 1-3 releases

added CI job token Category:Secrets Management GitLab Premium devopssoftware supply chain security grouppipeline security instrumentation missed:17.4 sectionsec typefeature workflowblocked labels

assigned to @iamricecake

removed missed:17.4 label

removed workflowblocked label

added pipelinetier-1 label

added analytics instrumentation analytics instrumentationreview pending backend labels

	2 Warnings
	59e4dbc4: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	59e4dbc4: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
analytics instrumentation	@nbelokolodov (UTC+13, 5 hours ahead of author)	Maintainer review is optional for analytics instrumentation
backend	@minahilnichols (UTC-5, 13 hours behind author)	@j_lar (UTC+1, 7 hours behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

• 3db3cbab - Track event when job token is authorized for a project with disabled scope

Compare with previous version

@fabiopitino can you please take a look and let me know if this provides the information that we need?

requested review from @fabiopitino

@nbelokolodov can you please do the analytics instrumentation review?

requested review from @nbelokolodov

added 1 commit

• 46125c54 - Track event when job token is authorized for a project with disabled scope

Compare with previous version

mentioned in issue #478522 (closed)

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

resolved all threads

enabled automatic add to merge train when checks pass

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 8cec06a6

expand test summary

+--------------------------------------------------------------+
|                        suites summary                        |
+---------+--------+--------+---------+-------+-------+--------+
|         | passed | failed | skipped | flaky | total | result |
+---------+--------+--------+---------+-------+-------+--------+
| Verify  | 38     | 0      | 1       | 0     | 39    | ✅     |
| Package | 25     | 0      | 0       | 0     | 25    | ✅     |
| Govern  | 17     | 0      | 0       | 0     | 17    | ✅     |
| Plan    | 4      | 0      | 0       | 0     | 4     | ✅     |
| Create  | 4      | 0      | 0       | 0     | 4     | ✅     |
| Secure  | 4      | 0      | 0       | 0     | 4     | ✅     |
| Release | 3      | 0      | 0       | 0     | 3     | ✅     |
+---------+--------+--------+---------+-------+-------+--------+
| Total   | 95     | 0      | 1       | 0     | 96    | ✅     |
+---------+--------+--------+---------+-------+-------+--------+

e2e-test-on-cng: test report for 8cec06a6

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Package     | 24     | 0      | 14      | 0     | 38    | ✅     |
| Plan        | 86     | 0      | 8       | 0     | 94    | ✅     |
| Analytics   | 2      | 0      | 0       | 1     | 2     | ✅     |
| Fulfillment | 2      | 0      | 7       | 1     | 9     | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Create      | 140    | 0      | 20      | 0     | 160   | ✅     |
| Verify      | 49     | 0      | 16      | 0     | 65    | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Govern      | 84     | 0      | 9       | 1     | 93    | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Secure      | 2      | 0      | 5       | 0     | 7     | ✅     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 436    | 0      | 119     | 3     | 555   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

@iamricecake some legit CI failures. Can you check?

aborted automatic add to merge train because the source branch was updated. Learn more.

added 1 commit

• 47241569 - Use extend to use tracking in class methods

Compare with previous version

reset approvals from @fabiopitino by pushing to the branch

added 832 commits

• 47241569...a8c2c9f2 - 829 commits from branch master
• 59e4dbc4 - Track event when job token is authorized for a project with disabled scope
• ba0003df - Use extend to use tracking in class methods
• 8cec06a6 - Clean up tracking calls

Compare with previous version

approved this merge request

added analytics instrumentationapproved label and removed analytics instrumentationreview pending label

removed review request for @nbelokolodov

requested review from @fabiopitino

approved this merge request

resolved all threads

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit c6d4a466

Hello @iamricecake

The Analytics Instrumentation team is actively working on improving the metrics implementation and event tracking processes. We would love to hear about your experience and any feedback you might have!

To provide your feedback, please use this Google Form.

Thanks for your help!

---

• Looking for existing metrics data? Check out the Metrics Exploration Dashboard for Group:pipeline_security.
• Need further assistance? Have comments?
  • Mention @gitlab-org/analytics-section/analytics-instrumentation/engineers
  • Reach out in #g_monitor_analytics_instrumentation channel on Slack.

This message was generated automatically. Improve it or delete it.

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-production label and removed workflowproduction label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label