Logstash clusters use configuration files to define plans to migrate data from different data sources (input) to different destinations (output).
You have obtained information about servers or clusters at the data source and destination, including IP addresses, usernames, and passwords.
Parameter | Description |
|---|---|
Name | User-defined configuration file name. It can contain only letters, digits, hyphens (-), and underscores (_), and must start with a letter. The minimum length is 4 characters. |
Configuration File Content | You can configure the configuration file content by modifying a template, and develop it from scratch. To use a configuration file template, expand System Templates or Custom Templates, select a template based on its description, and click Apply in the Operation column to copy the content of the template to the Configuration File Content area, where you can further modify relevant items.
NOTE: The size of each configuration file cannot exceed 100 KB. |
Hidden Content | For items that you enter in this box, the corresponding strings will be replaced with *** in the configurations. Enter sensitive strings that you want to hide, and press Enter. You can enter a maximum of 20 strings, each with a maximum length of 512 bytes. |
Parameter | Description |
|---|---|
pipeline.workers | Number of worker threads that will execute the Filters and Outputs stages of the pipeline in parallel. Value range: 1–20 Default value: Number of CPU cores |
pipeline.batch.size | Maximum number of events that a worker thread collects from inputs before attempting to execute its filters and outputs. A larger value is more effective but increases memory overhead. Default value: 125 |
pipeline.batch.delay | Maximum wait time for each new event before scheduling small batches to the pipeline worker thread and creating a pipeline event batch. Default value: 50 Unit: milliseconds. |
queue.type | An internal queue for event buffering.
Default value: memory |
queue.checkpoint.writes | Maximum number of written events before a forced checkpoint. This parameter needs to be set only when queue.type is set to persisted. Default value: 1024 |
queue.max_bytes | Total capacity of each persistent queue in MB. Ensure that the disk capacity is greater than this value. This parameter needs to be set only when queue.type is set to persisted. Default value: 1024 Unit: MB |
On the Configuration Center page, you can check the created configuration file. If its status changes to Available, it has been successfully created.
You can edit existing configuration files, set a configuration file as a custom template, and delete configuration files.
Function | Constraints | Operation Guide |
|---|---|---|
Modifying a configuration file | A configuration file that has an ongoing pipeline task cannot be modified. | In the configuration file list, find the row that contains the configuration file you want to edit, and click Edit in the Operation column. On the displayed page, you can modify Configuration File Content, Hidden Content, and pipeline parameters. |
Setting a configuration file as a template | N/A | In the configuration file list, click Add to Custom Template in the Operation column. In the displayed Add to Custom Template dialog box, set the template name, description, and configuration file content, and click OK. It can then be used as a template for configuring configuration files subsequently. |
Exporting configuration files | N/A | Click |
Deleting a configuration file | A configuration file that has an ongoing pipeline task cannot be deleted. | In the configuration list, find the row that contains the configuration file you want to delete, and click Delete in the Operation column. In the displayed dialog box, click OK. |