Feature request: Allow to filter environment in Organization Stats

[holledauer]

At the moment it is not possible to filter an environment in the organization stats (https://docs.sentry.io/api/organizations/get-organization-stats/). Ist it possible to add an environment filter? ?environment=production

[johannessjoberg]

Has this been taken into consideration? Would be a great addition 👍

[BYK]

Closing this issue due to staleness. Feel free to comment here if you think we should still work on this.

[holledauer]

still important...

[BYK]

Just checked the code and seems like we do have support for passing environment ids to the new TSDB models so it seems like this is just some wiring up in the API. Am I right @untitaker?

[untitaker]

you can do environment stats in discover already, and I believe tsdb queries related to environments boil down to a similar snuba query nowadays. We dont capture any environment info for rate-limited/dropped events.

[BYK]

@untitaker what I understand is that people can use the undocumented Discover API to run a Discover query?

[untitaker]

I don't know about that, but there are ways to get this data out of the Discover UI.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[mrdon]

My product, Sleuth, integrates with Sentry to pull down error counts, but because this feature is missing both here and for project stats, a number of shared customers have complained that it is broken. Please let me know what I can do to help, as I'd really like to avoid doing something like scraping the UI or using undocumented endpoints.

[leedongwei]

@mrdon There's no plans to allow filtering by environment in Organization Stats. This endpoint is intended for high-level tracking/reporting on usage.

The Discover endpoint might be more suitable for your use-case: https://docs.sentry.io/api/discover/query-discover-events-in-table-format/

[mrdon]

@leedongwei thanks. Looking at that API, am I correct in understanding that it returns a list of events, and at that, only 100 each request? Therefore, if a user had 10k events fire in that period, even if they were for the same issue, I would have to page 100 times?