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

Update azure monitor otel exporter to OTel 1.15 #28499

Merged
merged 5 commits into from
Jan 31, 2023
Merged

Conversation

jeremydvoss
Copy link
Member

@jeremydvoss jeremydvoss commented Jan 26, 2023

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

Updated log symbols. Severity moved to API. g/set_logger_provider moved
from SDK to internal API.
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@jeremydvoss jeremydvoss marked this pull request as ready for review January 28, 2023 00:06
Co-authored-by: Leighton Chen <lechen@microsoft.com>
@jeremydvoss
Copy link
Member Author

I left "The pull request does not introduce [breaking changes]" unchecked. While this pr does not affect the api layer, the version of OTel we are moving to does contain changes to some class paths and names. So, if a user is using this upcoming version of the exporter and also using OTel directly, they may need to update some of their imports from Otel's sdk and api

@lzchen lzchen merged commit 0d7aaf7 into Azure:main Jan 31, 2023
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.

3 participants