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.

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

[tracking] Monitoring and troubleshooting scenarios in the UI #962

Open
bryk opened this issue Jun 27, 2016 · 3 comments

Comments

@bryk
Copy link
Contributor

commented Jun 27, 2016

Goals: Add resource usage statistics/graphs to Kubernetes resources displayed in the UI. This is all that kubedash had plus other ways of facilitating monitoring use cases. This is, in particular, correlating events with metrics and aggregating metrics across multiple resources.

Work estimate: 1 eng for a quarter.

@bryk bryk changed the title [tracking] Monitoring and troubleshooting in the UI [tracking] Monitoring scenarios in the UI Jul 1, 2016

@bryk bryk changed the title [tracking] Monitoring scenarios in the UI [tracking] Monitoring and troubleshooting scenarios in the UI Jul 1, 2016

@bryk bryk added this to the 1.4 milestone Aug 19, 2016

@bryk bryk removed this from the 1.4 milestone Oct 24, 2016

@fejta-bot

This comment has been minimized.

Copy link

commented Dec 23, 2017

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

This comment has been minimized.

Copy link

commented Jan 22, 2018

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
/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Copy link

commented Feb 21, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.