Manage:Compliance | PPI | Unique users of audit events API

📡Telemetry Instrumentation

This will serve as the parent issue for the new tracking that needs to be implemented. This is related to the groupcompliance in GitLab.org / manage / general-discussion PPI issue.

📖 Reference - What data can be tracked currently?

Event Type	Snowplow JS (Frontend)	Snowplow Ruby (Backend)	Usage Ping	Database Import	Log System
Database Counts	❌	❌	✅	✅	❌
Pageview Events	✅	✅	❌	❌	❌
UI Events	✅	❌	❌	❌	❌
CRUD and API Events	❌	✅	❌	❌	❌
Event Funnels	✅	✅	❌	❌	❌
Postgres Data	❌	❌	❌	✅	❌
Logs	❌	❌	❌	❌	✅
External Services	❌	❌	❌	❌	❌

Documentation:

• Telemetry Direction Page
• Data for Product Managers
• North Star Metrics
• Telemetry Guide
• Usage Ping Guide
• Snowplow Guide

📖 What needs to be tracked?

• Database Counts
• Pageview Events
• CRUD / API Events
• Postgres Data
• Not sure (Telemetry will review)

Description of what needs to be tracked:

Usage of the audit events API as measured by unique users per month. (If 1 user makes requests to 3 different endpoints in a month, that is measured as 1 unique usage in that month.)

From the NSM issue discussion:

Snowplow ruby events are the way to go here. Snowplow JS, Snowplow Ruby do not have user_id tracking at this time. For now, you can implement per session tracking, not per user.

From a more recent thread in this issue:

We can use the same approach as the MR to track unique visitors to analytics pages.

Next steps (if any)

• Telemetry review complete (mark complete if not required)
• Child issues created