add prom link

bpmct · bpmct · commit c1de2b499131 · 2022-11-30T21:47:38.000Z
diff --git a/docs/admin/scale/index.md b/docs/admin/scale/index.md
@@ -34,4 +34,4 @@ coder loadtest create-workspaces \
 
 > To avoid user outages and orphaned resources, we recommend running scale tests on a secondary "staging" environment.
 
-If a test fails, you can leverage Coder's [performance tracing](#) and [prometheus metrics](#) to identify bottlenecks during scale tests. Additionally, you can use your existing cloud monitoring stack to measure load, view server logs, etc.
+If a test fails, you can leverage Coder's [performance tracing](#) and [prometheus metrics](../prometheus.md) to identify bottlenecks during scale tests. Additionally, you can use your existing cloud monitoring stack to measure load, view server logs, etc.

Original file line number	Diff line number	Diff line change
`@@ -34,4 +34,4 @@ coder loadtest create-workspaces \`
`34`	`34`
`35`	`35`	`> To avoid user outages and orphaned resources, we recommend running scale tests on a secondary "staging" environment.`
`36`	`36`
`37`		`-If a test fails, you can leverage Coder's [performance tracing](#) and [prometheus metrics](#) to identify bottlenecks during scale tests. Additionally, you can use your existing cloud monitoring stack to measure load, view server logs, etc.`
	`37`	`+If a test fails, you can leverage Coder's [performance tracing](#) and [prometheus metrics](../prometheus.md) to identify bottlenecks during scale tests. Additionally, you can use your existing cloud monitoring stack to measure load, view server logs, etc.`