Fluentd

We provide our own image of Fluentd to be run. We make use of our Fluentd plugin to save logs to Cassandra. https://github.com/motiv-labs/fluent-plugin-cassandra-driver

There are different images for Kubernetes vs. Docker-Compose. The provided Fluentd images and configs are intended to work specifically with Impulse. Other services and applications may not log in the same way and thus not work with our default Fluentd setup.

Be aware that the Note-Man service makes use of Fluentd’s HTTP source. If this is closed, the Note-Man application may not work as intended.

Docker-Compose Fluentd is run as a container in Docker-Compose. Docker containers whose logs should be sent to fluentd should use the Fluentd logging driver with a tag formatted like so:

**.impulse

Kubernetes Fluentd runs as a daemonset in kubernetes.

To start a new pod of Impulse’s provided Fluentd you will need to add the label beta.kubernetes.io/fluentd-ds-ready=true to every node you wish to run a Fluentd pod on.

Based on our config, if you want Fluentd to store the logs of a pod, you will need to add a label to the pod.

The label should be formatted like so: fluent-tag:

**.impulse