Add database query spans to otel traces

Implemented this. Only a lines on top of 📌 Allow assertions on the number of database queries run during tests RTBC .

Added testing instructions to the issue summary.

Interesting... maybe in the future we could build over ✨ [PP-1] Introduce a Connection::executeDdlStatement method Active and the dynamic queries API to provide more metadata as to the type of statement being executed - Data Definition (DDL), Data Manipulation (DML), etc...

See https://github.com/doctrine/dbal/blob/3.7.x/src/Connection.php#L1163-L1182 for definitions

If possible it would be great to at least get INSERT vs SELECT into the query events, both for assertions and for scannability here, but I'm not sure if we have access to that in the spot where those are populated.

We could by implementing some self describing metadata in the Database\Query classes and their extensions, and passing those into the events. Not immediate, but surely possible.

based on the IS this is postponed on 📌 Allow assertions on the number of database queries run during tests RTBC which is up for review but may be out of my wheelhouse but will try and keep an eye on it.

📌 Allow assertions on the number of database queries run during tests RTBC landed.

Much easier to review. THanks for also updating issue summary.

You got to it before me. But +1 on RTBC.

RTBC + 1

Committed and pushed 0907775505 to 11.x and 571aeb51d8 to 10.2.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.