support for opentelemetry db.query.summary calculation

[blumamir]

As this library already traverse the sql text and extract useful info like table names and commands, I wonder if you ever considered to also collect the db.query.summary text which is an opentelemetry semantic convention attribute with specification for how to build it.

I am not an expert myself, and cannot estimate if it's low or high effort and what are all the possible edge cases, but am curious if you have plans to support it anytime in the future, or if you already experimented with it and can share insights?

Could be so neat to have the ability to extract it in an opentelemetry collector processor and enhance the spans with this attribute. It can be super useful for metrics, analysis and UX (to show this value as the span name in trace views, and to be able to index and search by it).

Thanks again for the great work

[eric-weaver]

Hi @blumamir this is an interesting request. We don't currently have plans for handling the Otel db.query.summary calculation in go-sqllexer. I'd have to take a deeper look into the spec to get an idea of what the difficulty level of supporting this might be and whether this is the right place to do that. If this is something you have more immediate need for and would like to take a stab at coming up with a proposal for I'd be willing to look it over but currently limited on bandwidth to fully support this. Thank you for the request and we'll keep this in mind!