my main question: is it possible to make Sentry SDK route events to different DSNs / projects during runtime?
I’ve run into a problem when integrating the Sentry SDK into my employers codebase. On the backend, we have a fairly large system running on PHP. The system is deployed to a bunch of servers, and has a lot of configuration options and a few external API-integrations. In the case of misconfigurations, failed webservice calls etc., certain “high-level” errors are reported to our technical support staff, as they often can resolve these issues without involving the developers. Developers, on the other hand, are mostly concerned with the PHP errors / exceptions. To me, it makes sense to route PHP and these high-level errors to different projects, but I see no clear way of doing so without making ugly hacks.