Create a hitchhiker's guide for setting up monitoring in a namespace

operate-first / hitchhikers-guide

Hitchhiker's guide to Operate-first

GNU General Public License v3.0

3 stars 8 forks source link

Create a hitchhiker's guide for setting up monitoring in a namespace #110

Closed 4n4nd closed 2 years ago

4n4nd commented 3 years ago

[ ] Create notebook to show how to deploy a servicemonitor that starts metrics scraping
[ ] Create notebook to show how to add alerts on collected prometheus metrics

4n4nd commented 3 years ago

/priority important-longterm

sesheta commented 2 years ago

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.

/lifecycle stale

sesheta commented 2 years ago

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.

/lifecycle rotten

sesheta commented 2 years ago

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

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/hitchhikers-guide/issues/110#issuecomment-1073127229): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.