Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add StatsCollector to provide stats summary #4057

Closed
rjnagal opened this issue Feb 3, 2015 · 3 comments
Closed

Add StatsCollector to provide stats summary #4057

rjnagal opened this issue Feb 3, 2015 · 3 comments
Assignees
@vishh
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Milestone
v1.1

Comments

@rjnagal
Copy link
Contributor

rjnagal commented Feb 3, 2015

Add a new stats collector component that gather summary of node and pods usage from each node. This information can then be used by components like scheduler and autoscaler.

First version will expose node usage summary for cpu and memory. To start with, summary includes stats for average, maximum, and 90 percentile usage in last minute/hour/day. The stats are precomputed in cAdvisor and routed to the collector through kubelet.

@davidopp @bgrant0607
@rjnagal rjnagal added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Feb 3, 2015
@rjnagal rjnagal self-assigned this Feb 3, 2015
@davidopp
Copy link
Member

davidopp commented Feb 3, 2015

Sounds great. When Brian described this to me, he said the plan was to publish these as a new API object kind, and then link to the corresponding object from the PodStatus/NodeStatus (as opposed to inlining the resource usage info in the PodStatus/NodeStatus itself). This has benefits like allowing us to eventually store the resource updates in a separate etcd instance or whatever. Is this what you're planning to do?

@rjnagal
Copy link
Contributor Author

rjnagal commented Feb 3, 2015

That is roughly the plan. Although we have not yet settled on actual API object details.

I'll update them here soon.

@goltermann goltermann added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 4, 2015
@davidopp davidopp added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Feb 6, 2015
@bgrant0607 bgrant0607 mentioned this issue Feb 14, 2015
Closed
@bgrant0607 bgrant0607 mentioned this issue Apr 2, 2015
Closed
@bgrant0607 bgrant0607 added this to the v1.0 milestone Apr 16, 2015
@bgrant0607 bgrant0607 modified the milestones: v1.0-post, v1.0 Apr 27, 2015
@bgrant0607 bgrant0607 added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 27, 2015
@bgrant0607 bgrant0607 mentioned this issue May 20, 2015
Closed
@bgrant0607 bgrant0607 removed this from the v1.0-post milestone Jul 24, 2015
@bgrant0607 bgrant0607 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Aug 5, 2015
@bgrant0607 bgrant0607 added this to the v1.1 milestone Aug 5, 2015
@bgrant0607 bgrant0607 mentioned this issue Aug 5, 2015
Closed
@dchen1107
Copy link
Member

I am closing this one as dup of #12483

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vishh vishh

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
6 participants
@rjnagal @vishh @bgrant0607 @dchen1107 @davidopp @goltermann