Settings in the kuma-kont-config.yaml configuration file
The table lists the settings that you can specify in the kuma-kont-config.yaml file.
Settings in the kuma-kont-config.yaml configuration file
Setting |
Description |
---|---|
|
Optional setting in the General settings group. Used when debug level log output is required. If false, only start and stop messages are included, as well as errors that occurred during the sending process. Available values:
Default setting: false. |
|
An optional setting in the General settings group. This setting determines whether the utility reconnects to the database to make each request. Available values:
Default setting: false. |
|
Required setting in the General settings group. Absolute path to the JSON file in which the state of the processed logs is saved. The file is created automatically at this path. Make sure the user has sufficient permissions to write to this directory. Example: /home/user/kuma-kont/state.json |
|
Required setting in the General settings group. Absolute path to the log file for recording connector activity. The file is created automatically at this path. Make sure the user has sufficient permissions to write to this directory. Example: /home/user/kuma-kont/kuma-kont.log |
|
An optional setting in the General settings group. Database polling interval. The default value is 10 seconds. For high EPS, we recommend a value less than 15 seconds. |
|
Required setting in the Kontinent Database group. Name of the database in which Kontinent logs are received. |
|
Required setting in the Kontinent Database group. Name of the database user. |
|
Required setting in the Kontinent Database group. Password of the database user. |
|
Required setting in the Kontinent Database group. URL of the database server. |
|
Required setting in the Kontinent Database group. Port of the database server. Make sure it is accessible from the server where the utility is installed. |
|
Optional setting in the Kontinent Database group. Limit on the number of events that can be downloaded from the database as part of one poll. By default, 100,000 events per database poll. If EPS is high, we recommend a value equal or greater than this. |
|
Optional setting in the Last Id group. Specifies the event of the AlertLog type from which you want to start sending events to the KUMA collector. Only works on first run or when the state file does not exit. The default value is 0. |
|
Optional setting in the Last Id group. Specifies the event of the PacketLog type from which you want to start sending events to the KUMA collector. Only works on first run or when the state file does not exit. The default value is 0. |
|
Optional setting in the Last Id group. Specifies the event of the ServerAccessLog type from which you want to start sending events to the KUMA collector. Only works on first run or when the state file does not exit. The default value is 0. |
|
Optional setting in the Last Id group. Specifies the event of the SystemLog type from which you want to start sending events to the KUMA collector. Only works on first run or when the state file does not exit. The default value is 0. |
|
Required setting in the KUMA Collector group. Fully qualified domain name (FQDN) or IP address of the server where the KUMA collector is installed. |
|
Required setting in the KUMA Collector group. Port of the KUMA collector. |
|
Required setting in the KUMA Collector group. Data transfer protocol used by the KUMA collector. If the udp protocol is used, events are not resent if connection to the KUMA collector is lost. Available values:
|