-
Notifications
You must be signed in to change notification settings - Fork 200
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
feat(usage): include pvc name in volume events #1708
Conversation
From the usage analytics collected, it is hard to know why a particular type of storage engine is used over other. As the PVC names typically correspond to the application, this commit helps in adding PVC name to the volume events. The PVC name will be set as CampaignName property in analytics. Signed-off-by: kmova <kiran.mova@mayadata.io>
Signed-off-by: kmova <kiran.mova@mayadata.io>
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.
minor change suggestions, everything else looks good
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.
Ignore my older comment, I got your branch in local and figured out that the function sendEventOrIgnore
is different for local-pv provisioner and m-apiserver.
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.
lgtm
Once a PVC create request is processed by the CAST, the response is inspected to fetch the PVC name and other details to generate an analytics log. This was done as part of the PR: #1708 This commit adds a nil check to handle the case of an error response to avoid a panic. Signed-off-by: kmova <kiran.mova@mayadata.io>
Once a PVC create request is processed by the CAST, the response is inspected to fetch the PVC name and other details to generate an analytics log. This was done as part of the PR: #1708 This commit adds a nil check to handle the case of an error response to avoid a panic. Signed-off-by: kmova <kiran.mova@mayadata.io> (cherry picked from commit d70090d)
Once a PVC create request is processed by the CAST, the response is inspected to fetch the PVC name and other details to generate an analytics log. This was done as part of the PR: openebs-archive/maya#1708 This commit adds a nil check to handle the case of an error response to avoid a panic. Signed-off-by: kmova <kiran.mova@mayadata.io>
Once a PVC create request is processed by the CAST, the response is inspected to fetch the PVC name and other details to generate an analytics log. This was done as part of the PR: openebs-archive/maya#1708 This commit adds a nil check to handle the case of an error response to avoid a panic. Signed-off-by: kmova <kiran.mova@mayadata.io>
Why is this PR required? What issue does it fix?:
From the usage analytics collected, it is hard
to know why a particular type of storage engine
is used over other.
What this PR does?:
As the PVC names typically correspond to the
application, this commit helps in adding PVC name
to the volume events.
The PVC name will be set as CampaignName property
in analytics.
Does this PR require any upgrade changes?:
Not applicable
If the changes in this PR are manually verified, list down the scenarios covered::
Verified by creating cstor, jiva and Local PV volumes. The PVC name was sent as part of the campaign.
Any additional information for your reviewer? :
The changes done in this PR needs to be made for ZFS Local PV and CSI volumes as well.
Checklist:
<type>(<scope>): <subject>
Signed-off-by: kmova kiran.mova@mayadata.io