Overview
The FluentD output will stream analytics and insights to your FluentD endpoint.
Review Sample Configuration
The following sample configuration displays an output without the name of the organization-level integration:
- name: fluentd-log-fwd
type: fluentd
host: log-repo-host
port: 23131
encoder: msgpack
pool_size: 10
tag_prefix: "tail.ed."
features: log
Review Parameters
Review the following parameters that you can configure in the Edge Delta App.
name
Required
Enter a descriptive name for the output or integration.
For outputs, this name will be used to map this destination to a workflow.
Review the following example:
name: fluentd-log-fwd
integration_name
Optional
This parameter refers to the organization-level integration created in the Integrations page.
If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.
Review the following example:
integration_name: orgs-fluentd
type
Required
Enter fluentd.
Review the following example:
type: fluentd
host
Required
Enter the FluentD host. This parameter is required to support tcp stream.
Review the following example:
host: log-repo-host
port
Required
Enter the FluentD port. This parameter is required to support tcp stream.
Review the following example:
port: 23131
encoder
Optional
Enter the encoder type to use while streaming data to FluentD. Raw and 'msgpack' are supported.
Review the following example:
encoder: msgpack
tag_prefix
Optional
This parameter is used by the fluentd pusher to determine what fluentd tag to use. If the source config already defines a tag enrichment, then that configuration will be used. Otherwise, a tag will be generated in the following format: "{TagPrefix}{Agent's Tag}"
Review the following example:
tag_prefix: "tail.ed."
features
Optional
This parameter defines which data types to stream to the destination.
To learn more, review the Review Feature Types section in Stream Outputs and Integrations Overview.
Review the following example:
features: log
buffer_ttl
Optional
Enter a length of time to retry failed streaming data.
After this length of time is reached, the failed streaming data will no longer be tried.
Review the following example:
buffer_ttl: 2h
buffer_path
Optional
Enter a folder path to temporarily store failed streaming data.
The failed streaming data will be retried until the data reaches its destinations or until the Buffer TTL value is reached.
If you enter a path that does not exist, then the agent will create directories, as needed.
Review the following example:
buffer_path: /var/log/edgedelta/pushbuffer/
buffer_max_bytesize
Optional
Enter the maximum size of failed streaming data that you want to retry.
If the failed streaming data is larger than this size, then the failed streaming data will not be retried.
Review the following example:
buffer_max_bytesize: 100MB
Quick links