#Should an app be under two different projects
3 messages · Page 1 of 1 (latest)
2 projects seems the way to go here. They can have their own configuration and DSNs ("api" keys) this way. If you want to use the performance tracing features this will work just fine across projects with distributed tracing.
I have backend and frontend (and orchestrator, basically second backend) running under one project, and we separate them using beforeSend and initialContext setting the tag service: backend/frontend, so we can filter them