getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.53k stars 4.12k forks source link

Use environments for stats, spend allocation & inbound filters #52113

Open estahn opened 1 year ago

estahn commented 1 year ago

Problem Statement

We currently use 2 projects (ourapp-prod and ourapp-staging) to separate traces, errors, etc. This has the advantage that we can turn off staging if the volume is too high. The disadvantage of this is that we loose traceability of issues as they get resolved as they are not transferred across project boundaries as far as I can tell.

Environments is a key element of sentry but not utilised in a variety of areas such as:

Solution Brainstorm

No response

Product Area

Projects

getsantry[bot] commented 1 year ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 1 year ago

Routing to @getsentry/product-owners-projects for triage ⏲️

getsantry[bot] commented 1 year ago

Routing to @getsentry/product-owners-settings-projects for triage ⏲️

Dhrumil-Sentry commented 1 year ago

Hi @estahn Thanks for this feedback, I am adding this to our backlog but we're unlikely to work on this in the next few quarters.

One possible workaround is to create projects for different environments which will give you the granular controls you need

klemmchr commented 1 month ago

We are highly interested in this. Especially these two points

  • Stats - Clicking on stats, the reporting is only on project level
  • Spend allocation - Only available on project level, therefore I can not define "dev" or "staging" to have only X amount of performance insights per month.

Currently it's a guessing game for us which environment is causing which traffic and whether we need to tune it down.

getsantry[bot] commented 1 month ago

Routing to @getsentry/product-owners-stats for triage ⏲️