Is your feature request related to a problem? Please describe.
Some DbClientAttributesGetter implementations leverage SQL sanitization but do not extend SqlClientAttributesGetter. Changing their hierarchy while old database semantic conventions are supported would break legacy span names.
Describe the solution you'd like
After support for the old database semantic conventions is dropped, update the affected DbClientAttributesGetter implementations to extend SqlClientAttributesGetter.
Describe alternatives you've considered
Keep the current getter hierarchy until old database semantic convention support is removed.
Additional context
Follow-up from #12608. This work is blocked on dropping old database semantic conventions because it breaks old-semconv span names.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Is your feature request related to a problem? Please describe.
Some
DbClientAttributesGetterimplementations leverage SQL sanitization but do not extendSqlClientAttributesGetter. Changing their hierarchy while old database semantic conventions are supported would break legacy span names.Describe the solution you'd like
After support for the old database semantic conventions is dropped, update the affected
DbClientAttributesGetterimplementations to extendSqlClientAttributesGetter.Describe alternatives you've considered
Keep the current getter hierarchy until old database semantic convention support is removed.
Additional context
Follow-up from #12608. This work is blocked on dropping old database semantic conventions because it breaks old-semconv span names.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.