With this fluent-bit-plugin it is possible to send logs and metrics, which have been collected by fluent-bit, to a rabbitmq-exchange. Furthermore it is possible with this plugin to to store data fields from each collected log or metric into the routing-key .
Run the following command to build the plugin:
build| Parameter | Description | Default-Value |
|---|---|---|
| RabbitHost | The hostname of the Rabbit-MQ server | "" |
| RabbitPort | The port under which the Rabbit-MQ is reachable | "" |
| RabbitUser | The user of the Rabbit-MQ host | "" |
| RabbitPassword | The username of the user which connects to the Rabbit-MQ server | "" |
| ExchangeName | The exchange to which fluent-bit send its logs | "" |
| ExchangeType | The exchange-type | "" |
| RoutingKey | The routing-key pattern | "" |
| RoutingKeyDelimiter | The Delemiter which seperates the routing-key parts | "." |
| RoutingKeyDefaultValue | The routing-key default value to use if empty or error accessing | "" |
| RoutingKeyErrorOnEmpty | If enabled, fluentd errors on records without routing key or with empty routing key | "" |
| RemoveRkValuesFromRecord | If enabled fluentd deletes the values of the record, which have been stored in the routing-key | "" |
You can access values from each record an store them into the routing-key, by specifying a record-accessor.
$['key1'][0]["key2"]
The routing-key parts are delimited by the RoutingKeyDelimiter. If a string in one of the record-accesors containes the delimiter the plugin will not work as expected.
$["loglevel_3"].$["loglevel_1"][2]["sublevel"][0].$["loglevel_2"]["info_loglevel"]
This functionality has been implemented with the Record Accessor - Plugin Helper
If you want to run the plugin with the example config in /conf, you need to run the following command:
fluent-bit -e ./out_rabbitmq.so -c conf/fluent-bit-docker.conf