Skip to content

Improve Release Filtering: Enhance Package Name Management #88291

@serglom21

Description

@serglom21

Problem Statement

Currently, Sentry only allows the exclusion of specific release versions. This can be challenging in the mobile space, where repackaging and modifications are common.

For instance, if our official package name is com.example.app, we might encounter releases with slightly altered names like com.example.appa or com.example.appb. While I can exclude known variations, it's difficult to anticipate every possible modification.

This can sometimes lead to:

  • A somewhat cluttered Releases page, making it a bit harder to focus on official releases.
  • Potential challenges in accurately utilizing the "latest" release filter.
  • Increased noise within our event data, which could obscure genuine issues.

It would be great if there was a way to more easily filter out the unofficial releases.

Solution Brainstorm

  1. Refined Release Filters:
  • Current State of Release Filters: It primarily relies on explicitly excluding specific release versions. This approach becomes problematic when dealing with the dynamic nature of mobile app releases, where repackaging and modifications are common. To exclude multiple packages that we don't want, we must create an "OR" regex like ^com\.example\.appa@\d+\.\d+\.\d+$|^com\.example\.appb@\d+\.\d+\.\d+$. This method requires us to know and explicitly list every potential variation of the package name, which is often impossible. I attempted to use a negative lookahead regex such as com\.example\.(?!app@).*$ to exclude any release that did not begin with com.example.app@, but this did not work as expected.

  • Desire State of Release Filters: If these filters would allow me to specify release versions to "include" in addition to versions to "exclude", it would be great. More of less how the Sensitive Data Fields work for data scrubbing

  1. Designating "Official" Releases:
  • It might be helpful to introduce a feature that allows us to designate certain releases or package name patterns as "official." This could help Sentry automatically prioritize these releases.
  1. Refining the "latest" release filter:
  • It would be great to have the ability to refine the latest release filter, so that it can be filtered with regex or wildcards, or only show the latest release that is marked as official.

Product Area

Releases

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions