Skip to content

Correct formatting in scale-coder.md #21258

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

Open
eugeneotto wants to merge 3 commits into
base: main
Choose a base branch
from
+4 −4
Open

Correct formatting in scale-coder.md #21258

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b9350b9
Correct formatting in scale-coder.md
eugeneotto Dec 12, 2025
7dee312
Fix formatting of metrics capture bullet point
eugeneotto Dec 12, 2025
040523f
Reformat metrics capture bullet point
eugeneotto Dec 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/tutorials/best-practices/scale-coder.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ 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).
[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.
Expand All @@ -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
Expand Down
Loading