Skip to content

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

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
Closed
bryk opened this issue Jun 27, 2016 · 3 comments
Closed

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

bryk opened this issue Jun 27, 2016 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@bryk
Copy link
Contributor

bryk 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 mentioned this issue Jul 1, 2016
Closed
@maciaszczykm maciaszczykm added priority/P1 kind/feature Categorizes issue or PR as related to a new feature. labels Aug 9, 2016
@bryk bryk added this to the 1.4 milestone Aug 19, 2016
@maciaszczykm maciaszczykm mentioned this issue Sep 13, 2016
Closed
@bryk bryk removed this from the 1.4 milestone Oct 24, 2016
@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.

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

@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 Dec 23, 2017
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 22, 2018
@fejta-bot
Copy link

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

@maciaszczykm maciaszczykm reopened this Feb 21, 2018
@maciaszczykm maciaszczykm added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Feb 27, 2018
@maciaszczykm maciaszczykm removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1 labels Nov 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bryk @maciaszczykm @k8s-ci-robot @fejta-bot