Story

As an existing customer using the forwarder's fluentd output,
I want to upgrade to the vector-based collector and still forward logs to a remote fluentd server.

Description

Vector is not currently planning a fluent-forward sink (https://github.com/vectordotdev/vector/issues/534#issuecomment-1118973470)

As a workaround we can test using one of our existing vector outputs (syslog, kafka etc.) to forward to fluentd, and document this in a how-to for users.

Note the HTTP protocol, supported by vector and fluentd, would be a good choice. However we don't (yet) have a HTTP output in the CLF API so this would mean more work.

Acceptance Criteria

• Document the necessary changes to a fluent receiver config to be capable of receiving logs over http and continue to properly route them by tag
• Document a sample fluent.conf configuration to receive logs over http