Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
renovate
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
Renovate Bot
renovate
Commits
18e35bf4
Unverified
Commit
18e35bf4
authored
4 years ago
by
HonkingGoose
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
docs: explain log level numbers (#8704)
parent
8b0f0ab8
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/usage/self-hosting.md
+15
-0
15 additions, 0 deletions
docs/usage/self-hosting.md
with
15 additions
and
0 deletions
docs/usage/self-hosting.md
+
15
−
0
View file @
18e35bf4
...
@@ -421,3 +421,18 @@ spec:
...
@@ -421,3 +421,18 @@ spec:
It's recommended to configure `LOG_LEVEL=debug` and `LOG_FORMAT=json` in environment if you are ingesting/parsing logs into another system.
It's recommended to configure `LOG_LEVEL=debug` and `LOG_FORMAT=json` in environment if you are ingesting/parsing logs into another system.
Debug logging is usually necessary for any debugging, while JSON format will mean that the output is parseable.
Debug logging is usually necessary for any debugging, while JSON format will mean that the output is parseable.
### About the log level numbers
When you use `LOG_LEVEL=debug` and `LOG_FORMAT=json`, Renovate uses numbers in the `level` field.
The logging level output is controlled by the Bunyan logging library.
| Level | Meaning |
| ----: | ------- |
| 10 | trace |
| 20 | debug |
| 30 | info |
| 40 | warn |
| 50 | error |
| 60 | fatal |
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment