-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[baseserver] Add metric with version of the server, use in public api and usage #13022
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
f1d54e5
to
8051afb
Compare
@@ -37,7 +37,7 @@ func run() *cobra.Command { | |||
log.WithError(err).Fatal("Failed to get config. Did you specify --config correctly?") | |||
} | |||
|
|||
err = server.Start(cfg) | |||
err = server.Start(cfg, Version) |
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.
I see that this Version
is set during build, but how and where it is set and what is the format of the version string?
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.
I've observed either commit-<hash>
or main.<build-id>
It's set by the CI job when it builds the images
8051afb
to
bfb957c
Compare
/hold to not block merge Q |
/werft run 👍 started the job as gitpod-build-mp-baseserver-report-server-version-in-metric.4 |
/unhold |
Description
To be able to track which version we're on in our dashboards. Will produce the following metric:
Once validated, I can also add this to other instances of baseserver
The approach to the metric with version is standard, see docs
Related Issue(s)
Fixes #
How to test
Release Notes
Documentation
Werft options: