-
Notifications
You must be signed in to change notification settings - Fork 96
feat: add telemetry as part of mount options for blobfuse mounts #2248
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
Open
mittachaitu
wants to merge
5
commits into
kubernetes-sigs:master
Choose a base branch
from
mittachaitu:add_indicator
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+120
−4
Open
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7999704
chore: add telemetry as part of mount options for blobfuse mounts
mittachaitu 2b4e9c8
fix: add telemetry to the flag only if protocol is fuse2
mittachaitu 8d9b9fd
fix: move the tag adding logic inside blobfuse-proxy code
mittachaitu 5c45e5b
fix: update telemtery tag and add Unit test for telemetry parsing
mittachaitu 618aac5
fix: fix test case linting issue
mittachaitu 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 hidden or 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.
follow the PR example here: #2024 since protocol may be empty here, and also check whether this option is already specified
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.
btw, I think just use
--telemetry=aks/%sis more straightfowardThere 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.
Andy, I have moved the code to under pkg/blobfuse-proxy/server.go and if user specifies the option through StorageClass then we are appending above to telemetry option
ex: In below example user has provided telemetry as part of mount option...
Then mount args to blobfuse2 will be (--telemetry=azpartner-aks/v1.28.0,normaltest)
Note: If there is no
--telemetryin mount option then--telemetry=azpartner-aks/v1.28.0.The tag has been suggested by @vibhansa-msft, so not sure if there is any monitoring from blobfuse side