-
Notifications
You must be signed in to change notification settings - Fork 74
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GT-345 Optional JSON logger format (#1252)
- Loading branch information
Showing
7 changed files
with
61 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Logging configuration | ||
|
||
## Operator logging | ||
|
||
### Log level | ||
|
||
To adjust logging level of the operator, you can use `operator.args` in chart template value | ||
as described in [Additional configuration](./additional_configuration.md). | ||
|
||
For example, to set log level to `INFO` and `DEBUG` for `requests` package, you can use the following value: | ||
```yaml | ||
operator: | ||
args: ["--log.level=INFO", "--log.level=requests=DEBUG"] | ||
``` | ||
### Log format | ||
By default, operator logs in `pretty` format. | ||
|
||
To switch logging format to the JSON, you can use `operator.args` in chart template value: | ||
```yaml | ||
operator: | ||
args: ["--log.format=pretty"] | ||
``` | ||
|
||
## ArangoDeployment logging | ||
|
||
By default, ArangoDeployment logs in `pretty` format. | ||
|
||
To switch logging format to the JSON we need to pass `--log.use-json-format` argument to the ArangoDB server in the deployment: | ||
```yaml | ||
apiVersion: database.arangodb.com/v1 | ||
kind: ArangoDeployment | ||
metadata: | ||
name: single | ||
spec: | ||
mode: Single | ||
single: | ||
args: | ||
- --log.use-json-format | ||
- --log.level=INFO | ||
- --log.level=backup=TRACE | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.