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

Support for more granular control of what namespaces the scraper scrapes metrics from #12

Open
ghost opened this issue Jun 26, 2019 · 4 comments
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@ghost
Copy link

ghost commented Jun 26, 2019

API calls to metrics.k8s.io endpoint are cluster scoped. Is it possible to granularly control what namespaces the scraper scrapes from?

@ghost ghost changed the title Could we get support for more granular control of what namespaces the scraper scrapes metrics from Support for more granular control of what namespaces the scraper scrapes metrics from Jun 27, 2019
@jeefy
Copy link
Member

jeefy commented Jul 16, 2019

/assign

@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 Oct 14, 2019
@maciaszczykm
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 15, 2019
@ghost
Copy link
Author

ghost commented Oct 20, 2019

Since the plan is to ditch the metrics scraper, in favor of prometheus scraping directly. I think this can be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants