[db] Add docs for context info propagation
Relevant to #2162
Changes
Added documentations for instrumentations to propagate context information to databases
Merge requirement checklist
- [x] CONTRIBUTING.md guidelines followed.
- [x] Change log entry added, according to the guidelines in When to add a changelog entry.
- If your PR does not need a change log, start the PR title with
[chore]
- If your PR does not need a change log, start the PR title with
- [ ] schema-next.yaml updated with changes to existing conventions.
@open-telemetry/semconv-db-approvers, PTAL
Added documentations for instrumentations to propagate context information to databases
Should we clarify that this article is specific to MS SQL Server, since context_info is only available there? Other databases like Oracle and Postgres can use fields like v$session.action or application_name to propagate tracecontext.
Added documentations for instrumentations to propagate context information to databases
Should we clarify that this article is specific to MS SQL Server, since
context_infois only available there? Other databases like Oracle and Postgres can use fields like v$session.action or application_name to propagatetracecontext.
@nenadnoveljic I only added the context_info section to the SqlServer's documentation, so I believe we should be fine with that. What do you think?
I have refactored the PR to the following structure. @trask @nenadnoveljic @zacharycmontoya PTAL
- For every database
- Put
service.nameon sql comments.
- Put
- For sqlserver (extension)
- Put
traceparentvalue viaSET CONTEXT_INFO(opt-in)
- Put
Failed CI is irrelevant to this PR. https://github.com/open-telemetry/semantic-conventions/actions/runs/15172537474/job/42665853199?pr=2236 (fix)
This PR was marked stale due to lack of activity. It will be closed in 7 days.
Just saw this and very interested in any effort to clarify the role of sqlcommenter in OTel. @tammy-baylis-swi and i will be sharing our learnings at the Open Observability Summit June 26th, would love to talk about it with any maintainers or TC members there.
Superseded by #2495