Skip to content

fix(includes): use correct ERROR log level for STTRACE example #978

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
calmh merged 1 commit into from
Nov 23, 2025
Merged

fix(includes): use correct ERROR log level for STTRACE example #978

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
2 changes: 1 addition & 1 deletion includes/env-vars.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ STTRACE
generally mapping to a Go package. Enter a comma-separated string of
facilities to trace: ``api,beacon``. Optionally, a log level can be
given per facility to specify something other than DEBUG:
``api:WARN,beacon:ERR``, potentially overriding a global ``--log-level``
``api:WARN,beacon:ERROR``, potentially overriding a global ``--log-level``
adjustment.

The valid facility strings are listed below; additionally, ``syncthing
Expand Down