search

kubernetes-retired / spartakus

[EOL] Anonymous Usage Collector
Apache License 2.0
74 stars 30 forks source link

Collect stats on namespaces #3

Closed thockin closed 5 years ago

thockin commented 7 years ago
kenan435 commented 7 years ago

@thockin Any of you guys implementing this already? I have few of those namespace features already coded. I can finish the rest and make a PR.

thockin commented 7 years ago

Nobody is working on this yet. I'd be happy to review. This is the sort of thing that can be added as a series of very small commits, which makes reviews easy :)

On Tue, Sep 27, 2016 at 4:42 AM, Kenan Karamehmedovic < notifications@github.com> wrote:

@thockin https://github.com/thockin Any of you guys implementing this already? I have few of those namespace features already coded. I can finish the rest and make a PR.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes-incubator/spartakus/issues/3#issuecomment-249841188, or mute the thread https://github.com/notifications/unsubscribe-auth/AFVgVMSr__tyw5JwM98AmGBQc6MkVyZPks5quQERgaJpZM4KCbud .

dasmb commented 7 years ago

@kenan435 With the counts here, do you plan to provide the "last count," "average" or a histogram?

I believe histograms are the most powerful option, but don't know if there is a good histogram library for Golang.

thockin commented 7 years ago

I specifically meant a histogram, though we should make sure we have enough data points to do interesting analyses.

kenan435 commented 7 years ago

@dasmb, @thockin Please look at the README.md in my PR https://github.com/kubernetes-incubator/spartakus/pull/6/files#diff-04c6e90faac2675aa89e2176d2eec7d8R113 I have a sample .json output there. Basically we have a histogram for each k8s object we are monitoring. (Jobs, Svc, Deploy etc...). So if, for example, we have 100 jobs we would split that up into several buckets and collect info about each of the buckets.

fejta-bot commented 5 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.

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

fejta-bot commented 5 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.

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

fejta-bot commented 5 years ago

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 commented 5 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-incubator/spartakus/issues/3#issuecomment-503798374): >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](https://github.com/fejta). >/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.