Merge branch 'master' into create-pull-request/patch

Signed-off-by: Pat <[email protected]>

Author: patrick-stephens

SUMMARY.md

@@ -4,42 +4,28 @@ description: The production grade telemetry ecosystem
 
 # Fluentd and Fluent Bit
 
-Telemetry data processing can be complex, especially at scale. That's why
-[Fluentd](https://www.fluentd.org) was created. Fluentd is more than a simple tool,
-it's grown into a fullscale ecosystem that contains SDKs for different languages
-and subprojects like [Fluent Bit](https://fluentbit.io).
+Telemetry data processing can be complex, especially at scale. That's why [Fluentd](https://www.fluentd.org) was created. Fluentd is more than a simple tool, it's grown into a fullscale ecosystem that contains SDKs for different languages and subprojects like [Fluent Bit](https://fluentbit.io).
 
-Here, we describe the relationship between the [Fluentd](http://fluentd.org)
-and [Fluent Bit](http://fluentbit.io) open source projects.
+Here, we describe the relationship between the [Fluentd](http://fluentd.org) and [Fluent Bit](http://fluentbit.io) open source projects.
 
 Both projects are:
 
-- Licensed under the terms of Apache License v2.0.
-- Graduated hosted projects by the [Cloud Native Computing Foundation (CNCF)](https://cncf.io).
-- Production grade solutions: Deployed millions of times every single day.
-- Vendor neutral and community driven.
-- Widely adopted by the industry: Trusted by major companies like AWS, Microsoft,
-  Google Cloud, and hundreds of others.
+- Licensed under the terms of Apache License v2.0. - Graduated hosted projects by the [Cloud Native Computing Foundation (CNCF)](https://cncf.io). - Production grade solutions: Deployed millions of times every single day. - Vendor neutral and community driven. - Widely adopted by the industry: Trusted by major companies like AWS, Microsoft, Google Cloud, and hundreds of others.
 
-The projects have many similarities: [Fluent Bit](https://fluentbit.io) is
-designed and built on top of the best ideas of [Fluentd](https://www.fluentd.org)
-architecture and general design. Which one you choose depends on your end-users' needs.
+The projects have many similarities: [Fluent Bit](https://fluentbit.io) is designed and built on top of the best ideas of [Fluentd](https://www.fluentd.org) architecture and general design. Which one you choose depends on your end-users' needs.
 
 The following table describes a comparison of different areas of the projects:
 
 |  Attribute   | Fluentd               | Fluent Bit            |
 | ------------ | --------------------- | --------------------- |
 | Scope        | Containers / Servers  | Embedded Linux / Containers / Servers |
-| Language     | C & Ruby              | C                                     |
+| Language     | C and Ruby            | C                                     |
 | Memory       | Greater than 60 MB | Approximately 1 MB |
 | Performance  | Medium Performance    | High Performance                      |
 | Dependencies | Built as a Ruby Gem, depends on other gems. | Zero dependencies, unless required by a plugin. |
 | Plugins      | Over 1,000 external plugins available. | Over 100 built-in plugins available. |
 | License      | [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0) | [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0) |
 
-Both [Fluentd](https://www.fluentd.org) and [Fluent Bit](https://fluentbit.io)
-can work as Aggregators or Forwarders, and can complement each other or be used
-as standalone solutions.
+Both [Fluentd](https://www.fluentd.org) and [Fluent Bit](https://fluentbit.io) can work as Aggregators or Forwarders, and can complement each other or be used as standalone solutions.
 
-In the recent years, cloud providers have switched from Fluentd to Fluent Bit for
-performance and compatibility. Fluent Bit is now considered the next-generation solution.
+In the recent years, cloud providers have switched from Fluentd to Fluent Bit for performance and compatibility. Fluent Bit is now considered the next-generation solution.

about/fluentd-and-fluent-bit.md

@@ -5,16 +5,6 @@ description: Every project has a story
 
 # A brief history of Fluent Bit
 
-In 2014, the [Fluentd](https://www.fluentd.org/) team at
-[Treasure Data](https://www.treasuredata.com/) was forecasting the need for a
-lightweight log processor for constraint environments like embedded Linux and
-gateways. The project aimed to be part of the Fluentd ecosystem. At that moment,
-Eduardo Silva created [Fluent Bit](https://fluentbit.io/), a new open source solution,
-written from scratch and available under the terms of the
-[Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0).
+In 2014, the [Fluentd](https://www.fluentd.org/) team at [Treasure Data](https://www.treasuredata.com/) was forecasting the need for a lightweight log processor for constraint environments like embedded Linux and gateways. The project aimed to be part of the Fluentd ecosystem. At that moment, Eduardo Silva created [Fluent Bit](https://fluentbit.io/), a new open source solution, written from scratch and available under the terms of the [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0).
 
-After the project matured, it gained traction for normal Linux systems. With the
-new containerized world, the Cloud Native community asked to extend the 
-project scope to support more sources, filters, and destinations. Not long after,
-Fluent Bit became one of the preferred solutions to solve the logging challenges
-in Cloud environments.
+After the project matured, it gained traction for normal Linux systems. With the new containerized world, the Cloud Native community asked to extend the project scope to support more sources, filters, and destinations. Not long after, Fluent Bit became one of the preferred solutions to solve the logging challenges in Cloud environments.

about/history.md

@@ -5,9 +5,7 @@ description: Fluent Bit license description
 
 # License
 
-[Fluent Bit](http://fluentbit.io), including its core, plugins, and tools are
-distributed under the terms of the
-[Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0):
+[Fluent Bit](http://fluentbit.io), including its core, plugins, and tools are distributed under the terms of the [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0):
 
 ```text
                                  Apache License

about/license.md

@@ -4,7 +4,7 @@ description: >-
   Labs for learning how to best operate, use, and have success with Fluent Bit.
 ---
 
-# Sandbox and Lab Resources
+# Sandbox and lab resources
 
 ## Fluent Bit Sandbox - sign-up required
 

about/sandbox-and-lab-resources.md

@@ -4,24 +4,11 @@ description: Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
 
 # What is Fluent Bit?
 
-[Fluent Bit](https://fluentbit.io) is an open source telemetry agent specifically
-designed to efficiently handle the challenges of collecting and processing telemetry
-data across a wide range of environments, from constrained systems to complex cloud
-infrastructures. Managing telemetry data from various sources and formats can be a
-constant challenge, particularly when performance is a critical factor.
+[Fluent Bit](https://fluentbit.io) is an open source telemetry agent specifically designed to efficiently handle the challenges of collecting and processing telemetry data across a wide range of environments, from constrained systems to complex cloud infrastructures. Managing telemetry data from various sources and formats can be a constant challenge, particularly when performance is a critical factor.
 
-Rather than serving as a drop-in replacement, Fluent Bit enhances the observability
-strategy for your infrastructure by adapting and optimizing your existing logging
-layer, and adding metrics and traces processing. Fluent Bit supports a
-vendor-neutral approach, seamlessly integrating with other ecosystems such as
-Prometheus and OpenTelemetry. Trusted by major cloud providers, banks, and companies
-in need of a ready-to-use telemetry agent solution, Fluent Bit effectively manages
-diverse data sources and formats while maintaining optimal performance and keeping
-resource consumption low.
+Rather than serving as a drop-in replacement, Fluent Bit enhances the observability strategy for your infrastructure by adapting and optimizing your existing logging layer, and adding metrics and traces processing. Fluent Bit supports a vendor-neutral approach, seamlessly integrating with other ecosystems such as Prometheus and OpenTelemetry. Trusted by major cloud providers, banks, and companies in need of a ready-to-use telemetry agent solution, Fluent Bit effectively manages diverse data sources and formats while maintaining optimal performance and keeping resource consumption low.
 
-Fluent Bit can be deployed as an edge agent for localized telemetry data handling or
-utilized as a central aggregator/collector for managing telemetry data across
-multiple sources and environments.
+Fluent Bit can be deployed as an edge agent for localized telemetry data handling or utilized as a central aggregator/collector for managing telemetry data across multiple sources and environments.
 
 
 {% embed url="https://www.youtube.com/watch?v=3ELc1helke4" %}

about/what-is-fluent-bit.md

@@ -1,30 +1,22 @@
-# AWS Credentials
+# AWS credentials
 
-Plugins that interact with AWS services fetch credentials from the following providers
-in order. Only the first provider that provides credentials is used.
+Plugins that interact with AWS services fetch credentials from the following providers in order. Only the first provider that provides credentials is used.
 
 - [Environment variables](#environment-variables)
 - [Shared configuration and credentials files](#shared-configuration-and-credentials-files)
 - [EKS Web Identity Token (OIDC)](#eks-web-identity-token-oidc)
 - [ECS HTTP credentials endpoint](#ecs-http-credentials-endpoint)
 - [EC2 Instance Profile Credentials (IMDS)](#ec2-instance-profile-credentials-imds)
 
-All AWS plugins additionally support a `role_arn` (or `AWS_ROLE_ARN`, for
-[Elasticsearch](../pipeline/outputs/elasticsearch.md)) configuration parameter. If
-specified, the fetched credentials are used to assume the given role.
+All AWS plugins additionally support a `role_arn` (or `AWS_ROLE_ARN`, for [Elasticsearch](../pipeline/outputs/elasticsearch.md)) configuration parameter. If specified, the fetched credentials are used to assume the given role.
 
 ## Environment variables
 
-Plugins use the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` (and optionally
-`AWS_SESSION_TOKEN`) environment variables if set.
+Plugins use the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` (and optionally `AWS_SESSION_TOKEN`) environment variables if set.
 
 ## Shared configuration and credentials files
 
-Plugins read the shared `config` file at `$AWS_CONFIG_FILE` (or `$HOME/.aws/config`),
-and the shared credentials file at `$AWS_SHARED_CREDENTIALS_FILE` (or
-`$HOME/.aws/credentials`)  to fetch the credentials for the profile named
-`$AWS_PROFILE` or `$AWS_DEFAULT_PROFILE` (or "default"). See
-[Configuration and credential file settings in the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html).
+Plugins read the shared `config` file at `$AWS_CONFIG_FILE` (or `$HOME/.aws/config`), and the shared credentials file at `$AWS_SHARED_CREDENTIALS_FILE` (or `$HOME/.aws/credentials`)  to fetch the credentials for the profile named `$AWS_PROFILE` or `$AWS_DEFAULT_PROFILE` (or "default"). See [Configuration and credential file settings in the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html).
 
 The shared settings evaluate in the following order:
 
@@ -37,22 +29,16 @@ No other settings are supported.
 
 ## EKS Web Identity Token (OIDC)
 
-Credentials are fetched using a signed web identity token for a Kubernetes service account.
-See [IAM roles for service accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html).
+Credentials are fetched using a signed web identity token for a Kubernetes service account. See [IAM roles for service accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html).
 
 ## ECS HTTP credentials endpoint
 
-Credentials are fetched for the ECS task's role. See
-[Amazon ECS task IAM role](https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-iam-roles.html).
+Credentials are fetched for the ECS task's role. See [Amazon ECS task IAM role](https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-iam-roles.html).
 
 ## EKS Pod Identity credentials
 
-Credentials are fetched using  a pod identity endpoint. See
-[Learn how EKS Pod Identity grants pods access to AWS services](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html).
+Credentials are fetched using  a pod identity endpoint. See [Learn how EKS Pod Identity grants pods access to AWS services](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html).
 
 ## EC2 instance profile credentials (IMDS)
 
-Fetches credentials for the EC2 instance profile's role. See
-[IAM roles for Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html).
-As of Fluent Bit version 1.8.8, IMDSv2 is used by default and IMDSv1 might be disabled.
-Prior versions of Fluent Bit require enabling IMDSv1 on EC2.
+Fetches credentials for the EC2 instance profile's role. See [IAM roles for Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html). As of Fluent Bit version 1.8.8, IMDSv2 is used by default and IMDSv1 might be disabled. Prior versions of Fluent Bit require enabling IMDSv1 on EC2.