Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: fluentd rollout #442

Merged
merged 3 commits into from
Jan 12, 2020
Merged

FAQ: fluentd rollout #442

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c1c16da
add FAQ: fluentd rollout
drnickiw Mar 27, 2019
6b5f3cb
update fluentd FAQ
drnickiw Mar 27, 2019
98f9a4a
add tags to title and description for fluentd
drnickiw Apr 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions content/faq/fluentd-rollout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "How will `fluentd` be rolled out?"
description: "We deploy `fluentd` as a `DaemonSet` that runs on all nodes."
tags:
- fluentd
- DaemonSet
- logs
---

## Question

How will `fluentd` be rolled out?


## Answer

We deploy `fluentd` as a `DaemonSet` that runs on all nodes. It forwards/annotates all logs with contextual information, then ships it to a log sink. We've used Datadog logs, CloudWatch logs, and ElasticSearch. It supports a multitude of other backends, including Splunk and S3.

More information is available [here.](https://github.com/cloudposse/charts/tree/master/incubator/fluentd-kubernetes)