# Fluentd We provide our own image of Fluentd to be run. We make use of our Fluentd plugin to save logs to Cassandra. 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://motivlabs.gitbook.io/impulse-install-manual/fluentd.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.