Skip to content

Clarify db.query.summary for stored procedures #2218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
trask merged 9 commits into from
May 2, 2025
Merged

Clarify db.query.summary for stored procedures #2218

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
c2e6a4f
ansisql
trask May 2, 2025
e5dedde
chlog
trask May 2, 2025
5b5f28e
Update docs/database/database-spans.md
trask May 2, 2025
3b4fee8
format
trask May 2, 2025
b579ea1
both generic and sql server specific examples
trask May 2, 2025
de4fc6c
more clarification
trask May 2, 2025
9dc044e
more
trask May 2, 2025
6ae4c97
format
trask May 2, 2025
ec6fa38
Update .chloggen/2218.yaml
trask May 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/database/database-spans.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -458,7 +458,7 @@ name or target).
command.CommandText = "some_stored_procedure";
```

the corresponding `db.query.summary` is `EXECUTE some_stored_procedure`, `db.query.text` is not populated.
the corresponding `db.query.summary` is `CALL some_stored_procedure`, `db.query.text` is not populated.
Comment thread
trask marked this conversation as resolved.
Outdated

Semantic conventions for individual database systems or specialized instrumentations
MAY specify a different `db.query.summary` format as long as produced summary remains
Expand Down