Open kylannjohnson opened 1 year ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-releases for triage ⏲️
Routing to @getsentry/product-owners-dashboards for triage ⏲️
Hi @kylannjohnson, thanks for the feedback! We're aware that our Release filters and columns are very broad, but unfortunately we aren't able to prioritize this work currently and we will backlog this issue. The solution does involve storing more data by segmenting across the different release components, which currently isn't on our roadmap. I will bubble this up to the team for future concerns when dealing with releases
Routing to @getsentry/product-owners-releases for triage ⏲️
Routing to @getsentry/product-owners-dashboards for triage ⏲️
Problem Statement
In the Sentry releases console, I can filter the entires by package, build, stage, and version. However, these same values are not available to be a filter in a dashboard panel when i choose the Release data set.
It would be great if we could get the metrics that are calculated based off of a full Release (e.g. package@version+build). E.g. if we have the same version (e.g. 1.0), but in two variants (e.g. com.foo.free, com.foo.paid), then Sentry views those as separate releases so they have distinct error rates. Or, lets say I want to get the user counts from all users of 1.0. Because of the variation in package, the dashboards aren't capable of displaying it.
Solution Brainstorm
It would be great to be able to calculate all metrics via the release dashboard panels. I think this would mean indexing health envelopes on the components of a release, not the whole thing.
Product Area
Releases
┆Issue is synchronized with this Jira Improvement by Unito