Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit3c89e19

Browse files
committed
Clarified Prometheurs integration behavior
1 parentf650519 commit3c89e19

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

‎docs/admin/integrations/prometheus.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,8 @@ coderd_api_active_users_duration_hour 0
3131
###Kubernetes deployment
3232

3333
The Prometheus endpoint can be enabled in the[Helm chart's](https://github.com/coder/coder/tree/main/helm)
34-
`values.yml` by setting the environment variable`CODER_PROMETHEUS_ADDRESS` to
35-
`0.0.0.0:2112`. The environment variable`CODER_PROMETHEUS_ENABLE` will be
36-
enabled automatically. A Service Endpoint will not be exposed; if you need to
34+
`values.yml` by setting`CODER_PROMETHEUS_ENABLE=true`. Once enabled, the environment variable`CODER_PROMETHEUS_ADDRESS` will be set by default to
35+
`0.0.0.0:2112`. A Service Endpoint will not be exposed; if you need to
3736
expose the Prometheus port on a Service, (for example, to use a
3837
`ServiceMonitor`), create a separate headless service instead.
3938

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp