Fix Monitor:Respond GMAU double-counting
What does this MR do and why?
Fix Monitor:Respond GMAU double-counting.
There is already another PI used to count Respond GMAU. This change prevents double counting by reclassifying Linked Resources events.
Detailed background
Monitor:Respond has defined two GMAU metrics (4 in total, each one has a monthly and weekly version).
The handbook says here: "There should be a 1-1 mapping of Service Ping metrics to xMAU. We cannot dedupe users across distinct metrics, so multiple metrics mapped to a single group's GMAU, stage's SMAU, etc will lead to double-counting."
This means we're double-counting GMAUs.
@kbychu
suggested to reclassify redis_hll_counters.incident_management.issuable_resource_links_total_unique_counts_weekly.
Slack discussion (internal only).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.