Add Semantic definitions for Oracle Database#1911
Add Semantic definitions for Oracle Database#1911lmolkova merged 33 commits intoopen-telemetry:mainfrom
Conversation
* - Add semantic conventions for oracle database
(`db.operation.parameter.<key>`) in generic way.
Co-authored-by: Liudmila Molkova <[email protected]>
|
|
lmolkova
left a comment
There was a problem hiding this comment.
I believe the only unresolved discussion is around oracle.db.client.connection.implicit_release - suggesting to remove it and tackle in a follow-up PR along with transport span definition.
Thanks a lot for pushing through!
I have removed the attribute |
lmolkova
left a comment
There was a problem hiding this comment.
It looks great with a tiny caveat on the doc status.
Yes committed. Co-authored-by: Liudmila Molkova <[email protected]>
|
@alexkeh, @pfdsilva, @muhaook, you were working on introducing instrumentation to the Oracle .NET Clients directly. Could you please review? What is more, I think that you will need to update code in the clients. Reference of the old issue where we discussed it open-telemetry/opentelemetry-dotnet-instrumentation#3192 |
|
@Kielek I'm asking one of our Oracle team members to review this. Thanks for alerting us! |
Co-authored-by: Liudmila Molkova <[email protected]>
Fixes #
Changes
Add semantic conventions for Oracle Database.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]