Edge Delta FluentD Output

Overview

The FluentD output will stream analytics and insights to your FluentD endpoint.

Example

    - name: fluentd-log-fwd
      type: fluentd
      host: log-repo-host
      port: 23131
      encoder: msgpack
      pool_size: 10
      tag_prefix: "tail.ed."
      features: log

Parameters

name

The name parameter specifies a name for the data destination. You refer to this name in other places, for example to refer to a specific destination in a workflow. Names must be unique within the outputs section. It is a yaml list element so it begins with a - and a space followed by the string. A name is required for a data destinations.

outputs:
  streams:
    - name: <data destination name>

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.

integration_name: orgs-fluentd

type: fluentd

Required

The type parameter specifies a vendor or technology for the streaming data destination. It is a closed list element that requires one of the options. See the supported types here{target="_blank"}. A type is required for a streaming data destination.

outputs:
  streams:
    - name: <data destination name>
      type: <destination type>

host

Required

Enter the FluentD host. This parameter is required to support tcp stream.

host: log-repo-host

port

Required

Enter the FluentD port. This parameter is required to support tcp stream.

port: 23131

encoder

Optional

Enter the encoder type to use while streaming data to FluentD. Raw and ‘msgpack’ are supported.

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}”

tag_prefix: "tail.ed."

features

Optional

The features parameter specifies which types of data collected or generated by the agent to send to the output. It is written as a comma separated list. All streaming destinations support a features field but not all of them support the full list of datasets. For example, some destinations only support metrics. The features you can include are listed here. A feature is optional for a data destination.

outputs:
  streams:
    - name: <data destination name>
      type: <data destination type>
      features: <feature 1>, <feature 2> 

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.

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.

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.

buffer_max_bytesize: 100MB

custom_tags

Optional

This parameter defines key-value pairs that are streamed with every request.

custom_tags:
  "Host": "{{.Host}}"
  "Source": "{{.Source}}" 
  "SourceType": "{{.SourceType}}"
  "Tag": "{{.Tag}}"