From 2e2b46c38984e390850d6ecb25120629f2c69519 Mon Sep 17 00:00:00 2001
From: David Young <davidy@funkypenguin.co.nz>
Date: Tue, 22 Jan 2019 09:53:50 +1300
Subject: [PATCH] ctop is awesome

---
 manuscript/reference/troubleshooting.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/manuscript/reference/troubleshooting.md b/manuscript/reference/troubleshooting.md
index 494ac63..eac398b 100644
--- a/manuscript/reference/troubleshooting.md
+++ b/manuscript/reference/troubleshooting.md
@@ -16,6 +16,14 @@ SSH to the host node, and attach to the container using ```docker exec -it <cont
 
 Need to see what a particular container is doing? Run ```docker service logs -f <stack name>_<container name>``` to watch a particular service. As the service dies and is recreated, the logs will continue to be displayed.
 
+## Visually monitoring containers with ctop
+
+For a visual "top-like" display of your container's activity (_as well as a [detailed per-container view](https://github.com/bcicen/ctop/blob/master/_docs/single.md)_), try using [ctop](https://github.com/bcicen/ctop).
+
+To execute, simply run ```docker run --rm -ti --name ctop -v /var/run/docker.sock:/var/run/docker.sock quay.io/vektorlab/ctop:latest```
+
+Example:
+![](https://github.com/bcicen/ctop/raw/master/_docs/img/grid.gif)
 
 ## Chef's Notes