Skip to content

docs: clarified prometheus integration behavior #16724

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

Merged
merged 1 commit into from
Feb 26, 2025
Merged

docs: clarified prometheus integration behavior #16724

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
Clarified Prometheurs integration behavior
  • Loading branch information
@michaelvp411
michaelvp411 committed Feb 26, 2025
commit 3c89e196cf103a955cf4b6b7ed678cae4141d6a3
5 changes: 2 additions & 3 deletions docs/admin/integrations/prometheus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,8 @@ coderd_api_active_users_duration_hour 0
### Kubernetes deployment

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

Expand Down
Loading