Skip to content
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.

HNC: document instructions with Prometheus #433

Closed
adrianludwin opened this issue Feb 18, 2020 · 9 comments
Closed

HNC: document instructions with Prometheus #433

adrianludwin opened this issue Feb 18, 2020 · 9 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone

Comments

@adrianludwin
Copy link
Contributor

This is for @yeya24 due to his work on #416 - thanks Ben!

We're about to publish a doc for how to monitor HNC with Stackdriver. If you could write a doc about how to monitor with Prometheus, that would be great! You can write it any way you like (eg Google Doc, a new section in the README, etc). It doesn't need to be long - if you only need a paragraph or two (eg "Deploy Prometheus using operator X, and modify this resource to enable scraping") then that's even better.

@yeya24
Copy link
Contributor

yeya24 commented Feb 18, 2020

Thanks for the issue. Feel free to assign this to me. But I am busy this week. So maybe I can work on the doc this weekend. Is it ok?

@adrianludwin
Copy link
Contributor Author

adrianludwin commented Feb 18, 2020 via email

@adrianludwin
Copy link
Contributor Author

See #435 as a good model for this kind of doc.

@adrianludwin
Copy link
Contributor Author

Hi @yeya24 , are you still planning to work on this issue? Thanks!

@adrianludwin
Copy link
Contributor Author

@yeya24 Hi Ben, another update, are you planning on writing this? Thanks!

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 22, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 22, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants