Review and provide more description around Jira metrics
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
As we've been working on Jira integrations, we commonly have confusion around what our metrics are tracking. The descriptions are very sparse and it's critical to understand what each metric is tracking for us to make decisions about what we're prioritizing, as well as understanding what changes are making the most impact.
Example
I thought https://metrics.gitlab.com/keys/service-ping/?q=counts.projects_jira_active was comprehensive of all active Integrations per project. In discussion, one of our team members thought instead it was only representative of usage of the Basic Jira Integration. When investigating the usage here, we have charts covering jira_active, jira_cloud_active, and jira_server_active. We've learned that jira_active is the total between jira_cloud_active and jira_server_active. However, the total does not add up when investigating the cloud/server metrics individually.
Without more detail around each metric and due to the fact the two segmented metrics don't align with the total, it makes it difficult to validate and understand what these metrics are actually tracking.
Proposal
We should review each Jira metric and update the descriptions to be comprehensive, giving insight into the logic within the metric and clear details about what is being tracked.
It would make sense to address this as we work on Create `gitlab_for_jira_app_saas_active` and `g... (#375749)