Track parent/child/sibling "query id"s in Trino or generated queries to external sources

[sajjoseph]

Is it possible to track parent/child/sibling "query id"s in Trino?

Use case 1:
For PREPARE, EXECUTE, DESCRIBE and DEALLOCATE queries and related metadata queries, it will be great if there is a way we can track them using some sort of parent query id that all the related queries are associated with. It helps to track how many actual queries being triggered, wall time across queries, resource utilization etc.

Use case 2:
While querying a JDBC source, if we can somehow pass Trino query id to the remote data source, we can track the queries triggered from Trino to that remote source (one quick solution could be to add Trino query id as a comment to the generated SQL to the remote data source - #14500). It will be great to track it using a separate field though. This will help us to log it into "event logger" events and thus use for further analysis in the future.

Starburst team implemented QueryBand feature in their Teradata connector where they pass query id to Teradata engine so that Teradata folks can track all the queries coming from Starburst. A similar feature within Trino will be useful.

Thoughts?

[sajjoseph]

We could possibly use this PR to get some of this done - #14500.
@s2lomon - Thoughts?