We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The rewrite currently doesn't contain any k8up metrics.
The operator-sdk provides a default metrics endpoint though. So use that one to add the custom metrics, if possible.
Most metrics are defined in the observer or the scheduling in the old version: https://github.com/vshn/k8up/blob/master/service/schedule/scheduleRunner.go#L30 https://github.com/vshn/k8up/blob/master/service/observe/subscription.go#L23
With #114 merged the new implementation lives on the development branch.
The text was updated successfully, but these errors were encountered:
I'll take this one
Sorry, something went wrong.
@Kidswiss quick question related to this task: what’s the best way to setup prometheus in my local cluster for dev mode?
@susana-garcia I usually just curl'd the /metrics endpoint to see if the metrics show up. As they are plain text it's pretty easy to verify that way.
curl'd
/metrics
@Kidswiss ok, thanks!
susana-garcia
Successfully merging a pull request may close this issue.
The rewrite currently doesn't contain any k8up metrics.
The operator-sdk provides a default metrics endpoint though. So use that one to add the custom metrics, if possible.
Most metrics are defined in the observer or the scheduling in the old version:
https://github.com/vshn/k8up/blob/master/service/schedule/scheduleRunner.go#L30
https://github.com/vshn/k8up/blob/master/service/observe/subscription.go#L23
With #114 merged the new implementation lives on the development branch.
The text was updated successfully, but these errors were encountered: