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

Move fluent bit log collection to logs guide #26980

Merged
merged 3 commits into from
Jan 6, 2025
Merged

Move fluent bit log collection to logs guide #26980

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f94e9d0
Move fluent bit log collection to logs guide
estherk15 Jan 6, 2025
9148d7f
Add guide to log index
estherk15 Jan 6, 2025
9f1c271
Update content/en/logs/guide/fluentbit.md
estherk15 Jan 6, 2025
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
3 changes: 2 additions & 1 deletion content/en/logs/guide/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,9 @@ cascade:
{{< nextlink href="/logs/guide/apigee" >}}Collect Apigee Logs{{< /nextlink >}}
{{< nextlink href="/logs/guide/azure-logging-guide/" >}}Send Azure Logs to Datadog{{< /nextlink >}}
{{< nextlink href="/logs/guide/azure-native-logging-guide/" >}}Send Azure Logs with the Datadog Resource{{< /nextlink >}}
{{< nextlink href="/logs/guide/fluentbit" >}}Send Fluent Bit Logs{{< /nextlink >}}
{{< nextlink href="/integrations/google_cloud_platform/#log-collection" >}}Collect Google Cloud logs with the Datadog Dataflow template{{< /nextlink >}}
{{< nextlink href="/logs/guide/collect-google-cloud-logs-with-push/" >}}Collect Google Cloud logs with a Pub/Sub Push subscription{{< /nextlink >}}
{{< nextlink href="/logs/guide/collect-google-cloud-logs-with-push/" >}}Collect Google Cloud logs with a Pub/Sub Push subscription{{< /nextlink >}}
{{< nextlink href="logs/guide/collect-heroku-logs" >}}Collect Heroku Logs{{< /nextlink >}}
{{< nextlink href="logs/guide/log-collection-troubleshooting-guide" >}}Log Collection Troubleshooting Guide{{< /nextlink >}}
{{< nextlink href="logs/guide/docker-logs-collection-troubleshooting-guide" >}}Docker Log Collection Troubleshooting Guide{{< /nextlink >}}
Expand Down
18 changes: 5 additions & 13 deletions content/en/integrations/fluentbit.md → content/en/logs/guide/fluentbit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,29 +1,19 @@
---
title: Fluent Bit
title: Send Fluent Bit Logs to Datadog
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: Send Fluent Bit Logs to Datadog
title: Send Fluent Bit Logs to Datadog
aliases:
- /integrations/fluentbit/

Seems like we should include an alias for user who might try to access the old location?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The integrations-extras doc will take this url. I wasn't sure there would be a way to alias this without changing the integration files, so I opted to reference out to the guide in the intro. Do you think it would be better to change it on the integration side?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, gotcha. I think it is fine the way you did it then!

name: fluentbit
custom_kind: integration
description: 'Configure Fluent Bit to collect, parse, and forward log data from several sources.'
short_description: 'Collect, parse, and forward log data from several sources.'
categories:
- log collection
doc_link: /integrations/fluentbit/
dependencies:
['https://github.com/DataDog/documentation/blob/master/content/en/integrations/fluentbit.md']
has_logo: true
integration_title: Fluent Bit
is_public: true
public_title: Datadog-Fluent Bit Integration
further_reading:
- link: 'https://www.datadoghq.com/blog/fluentbit-integration-announcement/'
tag: 'Blog'
text: 'Centralize your logs with Datadog and Fluent Bit'
integration_id: "fluentbit"
---

## Overview

Configure Fluent Bit to collect, parse, and forward log data from several different sources to Datadog for monitoring. Fluent Bit has a small memory footprint (~450 KB), so you can use it to collect logs in environments with limited resources, such as containerized services and embedded Linux systems. [Datadog's Fluent Bit output plugin][1] supports Fluent Bit v1.3.0+.

To configure the Fluent Bit Agent check, see [Fluent Bit (Agent)][13].

## Setup

Find below instructions to configure Fluent Bit on a host, for Amazon ECS, see [ECS Fluent Bit and FireLens][2].
Expand Down Expand Up @@ -87,3 +77,5 @@ Need help? Contact [Datadog support][11].
[10]: /getting_started/tagging/
[11]: /help/
[12]: /logs/log_configuration/pipelines/?tab=host#preprocessing
[13]: /integrations/fluentbit/

Loading