From c13883e1c7e979f4207138f0e805fefdfdfa504d Mon Sep 17 00:00:00 2001 From: Tom Alexander Date: Sat, 1 Feb 2025 14:43:18 -0500 Subject: [PATCH] Fix link. --- posts/2025/02/01/graph-docker-memory/index.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2025/02/01/graph-docker-memory/index.org b/posts/2025/02/01/graph-docker-memory/index.org index ee1ce3c..b60a26e 100644 --- a/posts/2025/02/01/graph-docker-memory/index.org +++ b/posts/2025/02/01/graph-docker-memory/index.org @@ -7,7 +7,7 @@ #+select_tags: export #+exclude_tags: noexport -Sometimes it can be useful to build a graph of docker memory usage over time. For example, I was recently working on reducing the maximum memory of a long-running script. There certainly are heavy and complex options out there like setting up Prometheus and [[configuring docker to export metrics to it][https://docs.docker.com/engine/daemon/prometheus/]] but I threw together a small python script, using only the python standard library, that outputs gnuplot code to render a graph. +Sometimes it can be useful to build a graph of docker memory usage over time. For example, I was recently working on reducing the maximum memory of a long-running script. There certainly are heavy and complex options out there like setting up Prometheus and [[https://docs.docker.com/engine/daemon/prometheus/][configuring docker to export metrics to it]] but I threw together a small python script, using only the python standard library, that outputs gnuplot code to render a graph. * Usage