-
Notifications
You must be signed in to change notification settings - Fork 850
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
Fix/module name change #22258
Closed
Closed
Fix/module name change #22258
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
29be431
upgrade to latest version of azblob with test fixes
tanyasethi-msft ca546d6
Merge remote-tracking branch 'origin/main'
tanyasethi-msft 2f107ef
[azdatalake] STG 82 Preview
tanyasethi-msft 5195f1b
Merge remote-tracking branch 'origin/main'
tanyasethi-msft a784784
module name update
tanyasethi-msft 6e012f6
azdatalake recordings
tanyasethi-msft File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
As of
[email protected]
, themoduleName
param toazcore.NewClient()
takes the full module name instead of thepackage.ClientName
. So, all of these constants can go away.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.
All the three packages are already using
[email protected]
. What do you mean by full module name?The context here is that earlier we were passing
ModuleName
asazblob/service.Client
for example to create the azcore client from service client. In the telemetry policy, this is updated toservice.Client
from this code. This resulted in the user agent string asazsdk-go-service.Client/v1.2.0 (go1.19.3; Windows_NT)
.In this PR we are replacing
/
with.
in module name of respective clients which would give the user agent string,azsdk-go-azblob.service/v1.2.0 (go1.19.3; Windows_NT)
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.
Fully qualified module name e.g.
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob
.Originally, we wanted
package.ClientName
for use by the tracing policy. We've retooled how tracing works, so passingpackage.ClientName
is no longer necessary.Regarding the telemetry policy, we don't want/need the client name in the
User-Agent
string. See the guidelines for the format.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.
In current implementation, "azsdk-go-service.Client/v1.2.0 (go1.19.3; Windows_NT)" this user-agent string is not able to identify whether request was generated by "blob", "datalake" or "files" client as all three can have service client. Hence we are removing the "/" to include "azblob" or "azdatalake" in the string as well.
For the other part "service.Client" does not make much sense for telemetry in any way. If we are interested in just knowing which module was used then "azblob.service" itself tell the whole story ".client" is not adding any value there.
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.
On FE side we are building telemetry to parase the User-Agent string and dump some of the keywords to a dgrep table. Longer the string or more vivid the string, higher resource consumption between FE and XArgus. "azsdk-go-blob" shall be good enough for us to understand what SDK was used. Does Azure-SDK team have any sort of telemetry already built to identify which customers are using what SDK or which clients?