From b9350b9e85e9526f4f43664deebeca1b32dd4227 Mon Sep 17 00:00:00 2001 From: Eugene Otto Date: Fri, 12 Dec 2025 13:58:50 -0800 Subject: [PATCH 1/3] Correct formatting in scale-coder.md Fix indentation under a few bullet points. --- docs/tutorials/best-practices/scale-coder.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorials/best-practices/scale-coder.md b/docs/tutorials/best-practices/scale-coder.md index 7fbb55c10aa20..1d2abf4e17ed6 100644 --- a/docs/tutorials/best-practices/scale-coder.md +++ b/docs/tutorials/best-practices/scale-coder.md @@ -17,13 +17,13 @@ deployment. - Log output - Capture log output from from Coder Server instances and external provisioner daemons - and store them in a searchable log store like Loki, CloudWatch logs, or other tools. + and store them in a searchable log store like Loki, CloudWatch logs, or other tools. - Retain logs for a minimum of thirty days, ideally ninety days. This allows you investigate when anomalous behaviors began. - Metrics - Capture infrastructure metrics like CPU, memory, open files, and network I/O for all - Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances. + Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances. - Capture Coder Server and External Provisioner daemons metrics [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus). @@ -47,7 +47,7 @@ they affect the end-user experience. - Tail latency of Coder Server API requests - High tail latency can indicate Coder Server or the PostgreSQL database is underprovisioned - for the load. + for the load. - Use the `coderd_api_request_latencies_seconds` metric. - Tail latency of database queries From 7dee312d6881b5b5785280b2db06683977be72c8 Mon Sep 17 00:00:00 2001 From: Eugene Otto Date: Fri, 12 Dec 2025 14:00:13 -0800 Subject: [PATCH 2/3] Fix formatting of metrics capture bullet point --- docs/tutorials/best-practices/scale-coder.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/tutorials/best-practices/scale-coder.md b/docs/tutorials/best-practices/scale-coder.md index 1d2abf4e17ed6..3ef0f7adaf216 100644 --- a/docs/tutorials/best-practices/scale-coder.md +++ b/docs/tutorials/best-practices/scale-coder.md @@ -24,8 +24,7 @@ deployment. - Metrics - Capture infrastructure metrics like CPU, memory, open files, and network I/O for all Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances. - - Capture Coder Server and External Provisioner daemons metrics - [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus). + - Capture Coder Server and External Provisioner daemons metrics [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus). Retain metric time series for at least six months. This allows you to see performance trends relative to user growth. From 040523fc7964f1910240bfbe683564eaa546b9b1 Mon Sep 17 00:00:00 2001 From: Eugene Otto Date: Fri, 12 Dec 2025 14:00:47 -0800 Subject: [PATCH 3/3] Reformat metrics capture bullet point Reformat the metrics capture section for clarity. --- docs/tutorials/best-practices/scale-coder.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/tutorials/best-practices/scale-coder.md b/docs/tutorials/best-practices/scale-coder.md index 3ef0f7adaf216..e961a8873a73c 100644 --- a/docs/tutorials/best-practices/scale-coder.md +++ b/docs/tutorials/best-practices/scale-coder.md @@ -24,7 +24,8 @@ deployment. - Metrics - Capture infrastructure metrics like CPU, memory, open files, and network I/O for all Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances. - - Capture Coder Server and External Provisioner daemons metrics [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus). + - Capture Coder Server and External Provisioner daemons metrics + [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus). Retain metric time series for at least six months. This allows you to see performance trends relative to user growth.