Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

With DD plugin

Use the following configuration if you’re planning on using DD output plugin with fluent-bit:

  outputs: |
    [OUTPUT]
        Name datadog
        Match <match_pattern>
        Host <kfuse_ingress_ip>
        dd_message_key log
        TLS on
        compress gzip
	    apiKey random
        dd_tags <additional_tags>
	    dd_source <dd_source_name>
        dd_service <dd_service_name>

Note that the Host IP/DNS name in the above configuration can be the internal or external Kloudfuse ingress IP, depending on how you’ve configured the kfuse stack.

All the settings/configuration up to TLS on are required for the kfuse stack to work properly. The rest of the settings are recommended.

Without DD plugin

If you’re not planning on using DD output plugin, then you can use the HTTP plugin to push the logs to kfuse stack. Use the following configuration for HTTP plugin:

    [OUTPUT]
        Name http
        Match <match_pattern>
        Host <kfuse_ingress_ip>
        Port 80
        URI /ingester/v1/fluent_bit
        Format msgpack

Note that the Host IP/DNS name in the above configuration can be the internal or external Kloudfuse ingress IP, depending on how you’ve configured the kfuse stack.

Currently msgpack is the only supported format for HTTP plugin. You can also not include this setting. The default format for HTTP plugin is msgpack.

  • No labels