Skip to content

docs: Add details on what metrics are being exposed in operator-sdk #1168

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

Closed
lilic opened this issue Mar 5, 2019 · 2 comments · Fixed by #1522
Closed

docs: Add details on what metrics are being exposed in operator-sdk #1168

lilic opened this issue Mar 5, 2019 · 2 comments · Fixed by #1522
Assignees

Comments

@lilic
Copy link
Member

lilic commented Mar 5, 2019

See #719 (comment)

Documentation on what the actual metrics being exposed are.
Should we list out what exactly are the controller related metrics being recorded by the controller-runtime? And perhaps give an example of querying the endpoint to see these metrics in an example?
https://godoc.org/github.com/kubernetes-sigs/controller-runtime/pkg/internal/controller/metrics
https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/internal/controller/metrics/metrics.go#L50-L58
Number of reconciliations
Number of reconciliation errors per controller
Reconciliation duration
Resource metrics like CPU, memory usage, file descriptor usage
Go runtime metrics like number of Go routines, GC duration

@lilic lilic added docs labels Mar 5, 2019
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 3, 2019
@lilic
Copy link
Member Author

lilic commented Jun 4, 2019

/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2019
@lilic lilic self-assigned this Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants