-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix: property endpoint is ignored when using instrumentation_key #34399
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
Conversation
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Hi @dashpole , @pcwiese and @bogdandrutu , is there anyone could help to review this PR? thx! |
|
Looks like @pcwiese is the codeowner, and is the person you need to review before this can be merged |
|
Looks no response for about one month, could anyone else help on that or any suggestion? @dashpole @bogdandrutu |
dashpole
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix is trivial, so i'm approving. It would be good to have unit tests to catch these sorts of problems in general, though
…n-telemetry#34399) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Fixing a bug **Link to tracking Issue:** open-telemetry#33971 **Testing:** It's just one line and simple, so I just tested locally. If test cases needed, I can provide in this PR. **Documentation:** if no connection string and endpoint is provided, then use it instead of the default one. --------- Co-authored-by: David Ashpole <[email protected]>
Description:
Fixing a bug
Link to tracking Issue: #33971
Testing: It's just one line and simple, so I just tested locally. If test cases needed, I can provide in this PR.
Documentation: if no connection string and endpoint is provided, then use it instead of the default one.