You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our Android app, our CD system distributes builds for every main and MR branch to employees and other folks within the organization that are doing testing. These releases are internal and do not appear as release.stage:adopted. We'd like to be able to query these errors (coming from employees) separately from errors coming from end users (release.stage:adopted). Due to our process of promoting internal track builds to production, we don't want to use a separate versioning scheme for employee builds.
Solution Brainstorm
Add the ability in Discover (and in dashboards) to query from the Error data source by release.stage:adopted. Currently you can only do this on the "Releases" data source, but for Errors/events you can only do release:<specific version
Product Area
Discover
The text was updated successfully, but these errors were encountered:
@arifken thanks for raising this! It seems like tags would be a good solution here, does that work? If not, could you explain more what you're trying to achieve?
Problem Statement
For our Android app, our CD system distributes builds for every
main
and MR branch to employees and other folks within the organization that are doing testing. These releases are internal and do not appear asrelease.stage:adopted
. We'd like to be able to query these errors (coming from employees) separately from errors coming from end users (release.stage:adopted
). Due to our process of promoting internal track builds to production, we don't want to use a separate versioning scheme for employee builds.Solution Brainstorm
Add the ability in Discover (and in dashboards) to query from the Error data source by
release.stage:adopted
. Currently you can only do this on the "Releases" data source, but for Errors/events you can only dorelease:<specific version
Product Area
Discover
The text was updated successfully, but these errors were encountered: