Add max_exceeded log level option to automations & scripts (#14353)

This commit is contained in:
Phil Bruckner 2020-09-02 04:05:29 -05:00 committed by GitHub
parent 33de1d987e
commit 0ac2e4928c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 0 deletions

View File

@ -58,6 +58,8 @@ Mode | Description
For both `queued` and `parallel` modes, configuration option `max` controls the maximum
number of runs that can be executing and/or queued up at a time. The default is 10.
When `max` is exceeded (which is effectively 1 for `single` mode) a log message will be emitted to indicate this has happened. Configuration option `max_exceeded` controls the severity level of that log message. See [Log Levels](/integrations/logger/#log-levels) for a list of valid options. Or `silent` may be specified to suppress the message from being emitted. The default is `warning`.
#### Example Setting Automation Mode
```yaml

View File

@ -77,6 +77,11 @@ max:
required: false
type: integer
default: 10
max_exceeded:
description: "When `max` is exceeded (which is effectively 1 for `single` mode) a log message will be emitted to indicate this has happened. This option controls the severity level of that log message. See [Log Levels](/integrations/logger/#log-levels) for a list of valid options. Or `silent` may be specified to suppress the message from being emitted."
required: false
type: string
default: warning
sequence:
description: The sequence of actions to be performed in the script.
required: true