Web Vitals / Mobile: Regional Performance Metrics #75230
Assignees
Labels
Comments
DominikB2014
added a commit
to getsentry/relay
that referenced
this issue
Aug 8, 2024
work towards getsentry/sentry#75230 This PR adds country_code as an indexed span tag. Eventually we would like to create regional metrics, but we have to make a product decision on whether we want country based metrics, or larger region metrics (ex. continent). There are also ~200 countries, which could be high cardinality wise, but at least we have a known limit (lmk if you have thoughts on this!)
This was referenced Aug 12, 2024
DominikB2014
added a commit
to getsentry/relay
that referenced
this issue
Aug 13, 2024
Work towards getsentry/sentry#75230 This tags appropriate metrics with subregion as defined by the UN m49 standard. (There are many sources for this, for example see the tree under https://localizely.com/un-m49-list/). This allows us to filter down data by region within insight modules so that we can understand performance by region. Originally we were hoping to use country codes, but due to cardinality concerns, we opted for larger regions. There are a total of 22 geographical subregions vs 200+ countries. Note: I'm going to go through and double check all the mapping, but any early reviews of the implementation would be greatly appreciated. --------- Co-authored-by: David Herberth <[email protected]>
DominikB2014
added a commit
that referenced
this issue
Aug 13, 2024
Work towards #75230 Adds geo region selector, for now marked as "experimental" and internal only because we need to allow data to come in so its not always working. <img width="938" alt="image" src="https://github.com/user-attachments/assets/e60c71fc-b005-435c-a605-465f5acda2b1"> This will go in many other modules and areas of our app, but for now just web vitals landing for testing purposes. --------- Co-authored-by: Ash <[email protected]>
ameliahsu
pushed a commit
that referenced
this issue
Aug 13, 2024
Work towards #75230 Adds geo region selector, for now marked as "experimental" and internal only because we need to allow data to come in so its not always working. <img width="938" alt="image" src="https://github.com/user-attachments/assets/e60c71fc-b005-435c-a605-465f5acda2b1"> This will go in many other modules and areas of our app, but for now just web vitals landing for testing purposes. --------- Co-authored-by: Ash <[email protected]>
DominikB2014
added a commit
to getsentry/relay
that referenced
this issue
Aug 14, 2024
Work toward getsentry/sentry#75230 This PR allows mobile spans to be filtered down by subregion too. Anywhere we tag `device.class`, we also should also tag `user.geo.subregion` for this to work
DominikB2014
added a commit
that referenced
this issue
Aug 15, 2024
#76185) Work toward #75230 Adds geo selector in the web vitals and resource module and ensure all queries gets the filter applied NOTE: not all the metrics are properly tagged yet, so web vitals doesn't work entierely yet, and the resource module doesn't have geo data for resource size metrics. Its all behind a feature flag, so this not an issue that customers can see.
DominikB2014
added a commit
to getsentry/relay
that referenced
this issue
Aug 19, 2024
…3934) work towards getsentry/sentry#75230 This should allow all the asset module to be filtered down on user subregion.
This was referenced Sep 6, 2024
Merged
|
Note: I just had a user reach out in email asking for this functionality specifically. Good validation of this feature request (also let's make sure to follow up when this lands). |
|
Routing to @getsentry/product-owners-insights for triage ⏲️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ability to drill down by specific regions, e.g., eu, vs., north america, to see if performance varies by region.
We should research whether this is a common list of region names we could work from, e.g., CDN locations?
We also need to confirm if we collect ingest region information into span metrics.
The text was updated successfully, but these errors were encountered: