Project Namespaces

[jeengbe]

Problem Statement

Currently, Sentry's project hierarchy is flat. All projects lie in a single global namespace, which becomes increasingly unwieldy to manage, even when grouping resources by team.

This assumes that a project in Sentry is equivalent to one deployed unit (container).

Solution Brainstorm

• Allows grouping projects into namespaces similar to Kubernetes to prevent global name clashes.

I'm not dealing with many services in Sentry (a couple dozen), and this is starting to become an "issue". How is this managed in larger contexts where an organisation has many more projects?

---

long list

Product Area

Projects - Project Details

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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