getsentry
Use environments for stats, spend allocation & inbound filters
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:
- 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.
- Inbound filters - Not available, e.g. ignore all events from environment "dev"
Solution Brainstorm
No response
Product Area
Projects
![getsantry[bot] avatar](https://avatars.githubusercontent.com/in/66573?v=4 "Published by a pub.dev verified publisher"){kind=small}
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
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.
hi team, one of our other customers also requested the ability to set inbound filters by environment. is this something we have planned? thanks!
This is great feedback but not in our immediate plans. I'll resurface this to the team for future planning and if we slot it in will update this ticket.
Quick Question: Is there an API to get Sentry to get stats per environment? If so, that could be a good workaround for people who need this data.
