Database query naming #3419
Description
The customer wants to uniquely identify and track specific database queries in the Ruby agent. Currently, the agent groups queries heuristically under broad labels like
'Postgres Organization select', which makes it difficult to isolate individual queries—especially during performance regressions or incidents. In a recent high-severity incident, a problematic query was grouped with hundreds of others, delaying root cause analysis. The customer is looking for functionality similar to the .NET agent’s Database Query Naming feature to assign stable, meaningful names to distinct queries, enabling faster diagnostics and better query-level visibility.