[monitor/core] Update to Latest OpenTelemetry #26022
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JacksonWeber
requested review from
ckairen,
deyaaeldeen,
jeremymeng,
KarishmaGhiya,
sarangan12,
hectorhdzg,
joheredi and
mpodwysocki
as code owners
github-actions
bot
added
the
OpenTelemetry
jeremymeng
approved these changes
May 30, 2023
KarishmaGhiya
approved these changes
May 30, 2023
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
minhanh-phan
pushed a commit
to minhanh-phan/azure-sdk-for-js
that referenced
this pull request
Jun 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Packages impacted by this PR
@azure/core-http
@azure/core-rest-pipeline
@azure/opentelemetry-instrumentation-azure-sdk
@azure/monitor-opentelemetry-exporter
@azure/monitor-opentelemetry
Issues associated with this PR
microsoft/ApplicationInsights-node.js#1144
Describe the problem that is addressed by this PR
Update the latest OTel dependencies across the board.
Are there test cases added in this PR? (If not, why?)
This is just a dependency update.
Checklists