Record and allow to segment by database connections names #98699
Description
Problem Statement
As with many bigger apps, we have multiple database connections.
The queries tab is really useful, but it's hard to optimise when you can't segment or at least see against what database that query was made.
Solution Brainstorm
When sending a query to the Sentry in SDK (Laravel in our case, but I imagine it would be the same for other backend tech as well), attach the connection name. And allow to segment by connection in the UI.
Product Area
Insights