Is your change request related to a problem? Please describe.
When sending a command to a database, the parameters may have a type associated with them (in MSSQL they always have, not sure about other databases).
At the moment only the value of the parameter is stored, but not the type.
Describe the solution you'd like
Split db.query.parameter.<key> into
db.query.parameter.<key>.value which stores the value as previously db.query.parameter.<key>
db.query.parameter.<key>.type which stores the parameter type
Describe alternatives you've considered
One possibility would be to store the type as part of the value, like
db.query.parameter.foo=42 (Int32)
However parsing this now need special logic, especially for strings.
Area(s)
area:db
Is your change request related to a problem? Please describe.
When sending a command to a database, the parameters may have a type associated with them (in MSSQL they always have, not sure about other databases). At the moment only the value of the parameter is stored, but not the type.
Describe the solution you'd like
Split
db.query.parameter.<key>
intodb.query.parameter.<key>.value
which stores the value as previouslydb.query.parameter.<key>
db.query.parameter.<key>.type
which stores the parameter typeDescribe alternatives you've considered
One possibility would be to store the type as part of the value, like
However parsing this now need special logic, especially for strings.
Additional context
Related to https://github.com/open-telemetry/semantic-conventions/pull/866