Member Management Promotion Instrumentation

⚠ If GDK is accessible, an alternative to using this guide is to directly establish event/metric definitions using our internal events generator

Objective

Feature adoption and engagement

• How many unique namespaces engage with the Non-billable member controls feature? Specifically, those with the application setting set to true.
• Frequency with which users return to specific features over time? Monthly?

Events and Metrics

Definition of events and metrics | Sample metrics | Sample events

Details of metrics to be tracked:

Metric Description	Event / DB column to base the Metric on	Total or Unique Count of a Property	Time Frame	Feature
guest promotion control feature	Gitlab::CurrentSettings.enable_member_promotion_management	0 or 1	Monthly	🟠 [Add Controls for Ability to Promote Non-bill... (&13324 - closed)

In the rails console:

ApplicationSettings.last.enable_member_promotion_management yield a number of settings including enable_member_promotion_management which is default to true.

 "application_settings"."enable_member_promotion_management"
==> true

Gitlab::UsageData.data produces a long hash, however enable_member_promotion_management is not among them.

On the command line:

Running bin/rake gitlab:usage_data:dump_sql_in_json yields both SQL statements and data output that is used in the Service Ping, however enable_member_promotion_management is not among them.

I think we'll have to create our own instrumentation in order to have this setting data flow from instance through the service ping and eventually into snowflake.

Expand to view examples and guidelines for filling the table

Metrics:

• Description: What quantitative measurements derived from either event data or database columns would you like to track? eg: Monthly Count of Instances with enable_member_promotion_management set to true.
• Event/DB column: What event or database column should the metric count or be based on. ApplicationSettings#enable_member_promotion_management
• Total or unique count: Should the metric count all occurrences or only unique counts, e.g. of user_id to get a count of unique users triggering an event. Total
• Time Frame: What time frames should be tracked. Default and recommended is 7d and 28d.

Next steps

• Assign an engineering counterpart from your group to add instrumentation to the code
• Explore instrumented data with the help of our data discovery guide. You can also reach out to product data insights team for help with generating Tableau reports/dashboards.
• Your feedback is valuable to us. Please leave us feedback in the comment section of this issue and tag @tjayaramaraju or @Basti

Important links

⭐ Quick start guide to internal events

❓ Analytics Instrumentation slack channel for questions

✍ Try our internal events generator. Creating event and metric definition files has never been easier.