Skip to content
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.

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

Rename SqlClientInstrumentationOptions to SqlClientTraceInstrumentationOptions #5285

Conversation

Kielek
Copy link
Contributor

@Kielek Kielek commented Jan 30, 2024

Fixes #
Design discussion issue #
Propagate changes from #5109

Changes

Rename SqlClientInstrumentationOptions to SqlClientTraceInstrumentationOptions.

Merge requirement checklist

  • CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
  • Unit tests added/updated
  • Appropriate CHANGELOG.md files updated for non-trivial changes
  • Changes in public API reviewed (if applicable)

@Kielek Kielek requested a review from a team as a code owner January 30, 2024 05:55
Copy link

codecov bot commented Jan 30, 2024

Codecov Report

Attention: 21 lines in your changes are missing coverage. Please review.

Comparison is base (6250307) 83.38% compared to head (bfd95e3) 82.98%.
Report is 45 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5285      +/-   ##
==========================================
- Coverage   83.38%   82.98%   -0.40%     
==========================================
  Files         297      272      -25     
  Lines       12531    11973     -558     
==========================================
- Hits        10449     9936     -513     
+ Misses       2082     2037      -45     
Flag Coverage Δ
unittests ?
unittests-Instrumentation-Experimental 24.66% <47.22%> (?)
unittests-Instrumentation-Stable 24.66% <47.22%> (?)
unittests-Solution-Experimental 82.72% <76.92%> (?)
unittests-Solution-Stable 82.97% <76.92%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
....Api/Context/Propagation/TraceContextPropagator.cs 90.00% <100.00%> (+0.52%) ⬆️
...etryProtocol/Implementation/ExperimentalOptions.cs 100.00% <ø> (ø)
...tation/OpenTelemetryProtocolExporterEventSource.cs 100.00% <100.00%> (ø)
...rotocol/Implementation/OtlpLogRecordTransformer.cs 93.45% <100.00%> (ø)
...tation.AspNetCore/Implementation/HttpInListener.cs 89.79% <100.00%> (+0.21%) ⬆️
...AspNetCore/Implementation/HttpInMetricsListener.cs 89.74% <100.00%> (+0.26%) ⬆️
...ntation.GrpcNetClient/GrpcClientInstrumentation.cs 100.00% <100.00%> (ø)
...NetClient/GrpcClientTraceInstrumentationOptions.cs 100.00% <ø> (ø)
...ent/Implementation/GrpcClientDiagnosticListener.cs 75.80% <100.00%> (-2.77%) ⬇️
...n.GrpcNetClient/TracerProviderBuilderExtensions.cs 100.00% <100.00%> (ø)
... and 13 more

... and 30 files with indirect coverage changes

@Kielek Kielek force-pushed the instrumentation-sqlclient-rename-options-class branch from c683282 to 8f660a7 Compare January 30, 2024 06:03
@alanwest alanwest merged commit d2f9d05 into open-telemetry:main Jan 31, 2024
43 of 44 checks passed
@smoms
Copy link

smoms commented May 31, 2024

May I understand how come a breking change like this is just increasing a patch number? Does not follow semantic release? tks

@vishweshbankwar
Copy link
Member

vishweshbankwar commented May 31, 2024

May I understand how come a breking change like this is just increasing a patch number? Does not follow semantic release? tks

This component is now moved to https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main

Please take a look at this note: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/47b667acf8cde47aa73fc6d28b609ebb3aeca8d3/src/OpenTelemetry.Instrumentation.SqlClient/README.md?plain=1#L20-L29

@Kielek Kielek deleted the instrumentation-sqlclient-rename-options-class branch June 1, 2024 06:10
@smoms
Copy link

smoms commented Jun 1, 2024

@vishweshbankwar thanks. Does it mean that now the package is being moved to stable?

@cijothomas
Copy link
Member

@vishweshbankwar thanks. Does it mean that now the package is being moved to stable?

If you are referring to https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.SqlClient, then no. It is not moved to stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants