Sentry - Project organization across environments (clutter)


#1

I’m taking a look at Sentry, but I am struggling to decide how I would best structure our projects across environments.

We have a backend consisting of several microservices with some shared code (utils etc.). My idea is to set up 1 Sentry project for this entire backend, and then use a ServiceName tag (or similar) to make filtering errors per microservice possible.

Now, we have 3 environments that I would like to cover: dev, staging and prod. If I use a single project for all 3 environments, the dashboard gets cluttered due to the larger amount of errors that occur in dev+staging and getting an overview of the production errors means I have to apply a filter first.

Is the suggested method to create a project per environment, or at least a separate project for production, and then another for dev/staging combined?