-
Notifications
You must be signed in to change notification settings - Fork 3
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: reporting back installation and upgrade metrics #92
feat: reporting back installation and upgrade metrics #92
Conversation
efafc68
to
771dbeb
Compare
reporting back installation and upgrades data.
771dbeb
to
7b46dd5
Compare
cmd/helmvm/token.go
Outdated
encodedToken := bytes.NewBuffer(nil) | ||
encoder := base64.NewEncoder(base64.StdEncoding, encodedToken) | ||
marshaler := json.NewEncoder(encoder) | ||
if err := marshaler.Encode(token); err != nil { |
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.
How about an Encode() function on the JoinToken struct?
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.
that makes sense. done.
pkg/metrics/sender.go
Outdated
url := fmt.Sprintf("%s/helmbin_metrics/%s", s.baseURL, ev.Title()) | ||
payload, err := s.payload(ev) | ||
if err != nil { | ||
logrus.Infof("unable to get payload for event %s: %s", ev.Title(), err) |
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.
Why is this info and the rest level debug?
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.
my bad, it should have been a debugf as well. fixed.
we are using debugf in all other logrus calls except one.
7011b73
to
4bb7cbf
Compare
Reporting back Installation, Join, and Upgrades data. This work is described in details here.
HelmVM adoption metrics
The reporting is based on events, some events will be generated by the installer (that this PR implements) and some by an operator running on the cluster (still to be implemented). The operator is responsible for keeping track of the nodes that compose the cluster while the installer is responsible for reporting installation, upgrades, and joins successes and failures.
These are the events reported through this PR:
This PR depends on https://github.com/replicatedhq/vandoor/pull/4333.