Deprecation complete: gpus ... (#3537)

This commit is contained in:
Steve Perry
2017-04-25 20:09:38 -07:00
committed by GitHub
parent f83c5874a8
commit 80a2fff4dc
20 changed files with 29 additions and 106 deletions
@@ -6,6 +6,9 @@ title: Logging and Monitoring Cluster Activity
redirect_from:
- "/docs/concepts/clusters/logging/"
- "/docs/concepts/clusters/logging.html"
redirect_from:
- "/docs/user-guide/logging/overview/"
- "/docs/user-guide/logging/overview.html"
---
Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism; as such, most container engines are likewise designed to support some kind of logging. The easiest and most embraced logging method for containerized applications is to write to the standard output and standard error streams.
@@ -2,6 +2,9 @@
assignees:
- mikedanese
title: Resource Usage Monitoring
redirect_from:
- "/docs/user-guide/monitoring/"
- "/docs/user-guide/monitoring.html"
---
Understanding how an application behaves when deployed is crucial to scaling the application and providing a reliable service. In a Kubernetes cluster, application performance can be examined at many different levels: containers, [pods](/docs/user-guide/pods), [services](/docs/user-guide/services), and whole clusters. As part of Kubernetes we want to provide users with detailed resource usage information about their running applications at all these levels. This will give users deep insights into how their applications are performing and where possible application bottlenecks may be found. In comes [Heapster](https://github.com/kubernetes/heapster), a project meant to provide a base monitoring platform on Kubernetes.