Skip to content

Commit

Permalink
Updating README for the additional log time format argument
Browse files Browse the repository at this point in the history
  • Loading branch information
sstk-tbickford committed Apr 21, 2020
1 parent 2fdaf05 commit 591c7ce
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,12 +168,16 @@ to deploy it as part of KEDA. Do the following:
You can change default log levels for both KEDA Operator and Metrics Server. KEDA Operator uses [Operator SDK logging](https://github.com/operator-framework/operator-sdk/blob/master/doc/user/logging.md) mechanism.

### KEDA Operator logging
Find `--zap-level=` argument in Operator Deployment section in `deploy/12-operator.yaml` file, modify it's value and redeploy.
To change the logging level, find `--zap-level=` argument in Operator Deployment section in `deploy/12-operator.yaml` file, modify it's value and redeploy.
Allowed values are `debug`, `info`, `error`, or an integer value greater than `0`, specified as string
Default value: `info`
To change the logging time format, find `--zap-time-encoding=` argument in Operator Deployment section in `deploy/12-operator.yaml` file, modify it's value and redeploy.

Allowed values are `epoch`, `millis`, `nano`, or `iso8601`

### Metrics Server logging
Find `--v=0` argument in Operator Deployment section in `deploy/22-metrics-deployment.yaml` file, modify it's value and redeploy.
Expand Down

0 comments on commit 591c7ce

Please # to comment.