When looking through SQL statement details, it is not revealed what database it was executed against. Currently the systems I monitor have about 15 databases. In a prior job, a single server could have over 150.
More often than not, the query itself may not be overly informative of which database it is for. (with 150 identical schema copies of the same template database, who is killing the server updating their USERS table?)
Obviously it may be unrealistic to track a query that crosses databases as it does so. That is more of an exercise for the customer.