opensource/coder
3
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2026-10-29 17:44:33 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: use CODER_LOG_FILTER instead of CODER_VERBOSE (#19105)

Browse Source 
closes #18833

replace suggestions to use the now-deprecated `CODER_VERBOSE` with more
specific `CODER_LOG_FILTER`

thanks @UnicornyRainbow!

---------

Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>
This commit is contained in:
Edward Angert
2025-07-30 12:35:45 -04:00
committed by GitHub
co-authored by EdwardAngert
parent 428ec351fe
commit 998fbdfbb3
3 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin/monitoring/notifications/index.md
+1 -1
View File
@@ -282,7 +282,7 @@ troubleshoot:
1. Review the logs. Search for the term `notifications` for diagnostic information. 1. Review the logs. Search for the term `notifications` for diagnostic information.
- If you do not see any relevant logs, set - If you do not see any relevant logs, set
`CODER_VERBOSE=true` or `--verbose` to output debug logs. `CODER_LOG_FILTER=".*notifications.*"` to filter for notification-related logs.
1. If you are on version 2.15.x, notifications must be enabled using the 1. If you are on version 2.15.x, notifications must be enabled using the
`notifications` `notifications`
[experiment](../../../install/releases/feature-stages.md#early-access-features). [experiment](../../../install/releases/feature-stages.md#early-access-features).
docs/admin/users/idp-sync.md
+1 -2
View File
@@ -203,7 +203,7 @@ Visit the Coder UI to confirm these changes:
### Group allowlist ### Group allowlist
You can limit which groups from your identity provider can log in to Coder with You can limit which groups from your identity provider can log in to Coder with
[CODER_OIDC_ALLOWED_GROUPS](https://coder.com/docs/cli/server#--oidc-allowed-groups). [CODER_OIDC_ALLOWED_GROUPS](../../reference/cli/server.md#--oidc-allowed-groups).
Users who are not in a matching group will see the following error: Users who are not in a matching group will see the following error:
<Image height="412px" src="../../images/admin/group-allowlist.png" alt="Unauthorized group error" align="center" /> <Image height="412px" src="../../images/admin/group-allowlist.png" alt="Unauthorized group error" align="center" />
@@ -419,7 +419,6 @@ If you are running into issues with a sync:
1. To reduce noise, you can filter for only logs related to group/role sync: 1. To reduce noise, you can filter for only logs related to group/role sync:
```sh ```sh
CODER_VERBOSE=true
CODER_LOG_FILTER=".*userauth.*|.*groups returned.*" CODER_LOG_FILTER=".*userauth.*|.*groups returned.*"
``` ```
docs/admin/users/oidc-auth/index.md
+1 -1
View File
@@ -27,7 +27,7 @@ claims from the ID token and the claims obtained from hitting the upstream
provider's `userinfo` endpoint, and use the resulting data as a basis for provider's `userinfo` endpoint, and use the resulting data as a basis for
creating a new user or looking up an existing user. creating a new user or looking up an existing user.
To troubleshoot claims, set `CODER_VERBOSE=true` and follow the logs while To troubleshoot claims, set `CODER_LOG_FILTER=".*got oidc claims.*"` and follow the logs while
signing in via OIDC as a new user. Coder will log the claim fields returned by signing in via OIDC as a new user. Coder will log the claim fields returned by
the upstream identity provider in a message containing the string the upstream identity provider in a message containing the string
`got oidc claims`, as well as the user info returned. `got oidc claims`, as well as the user info returned.