You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it may be ok(?) to capture the full value under db.query.text and users can rely on the general attribute limit to truncate
But I think it may make sense to apply some kind of limit to db.query.summary (or at least to the resulting span name when it is based on db.query.summary).
The text was updated successfully, but these errors were encountered:
In Java Instrumentation repo, we've had reports of query texts of 15mb.
I think it may be ok(?) to capture the full value under
db.query.text
and users can rely on the general attribute limit to truncateBut I think it may make sense to apply some kind of limit to
db.query.summary
(or at least to the resulting span name when it is based ondb.query.summary
).The text was updated successfully, but these errors were encountered: