Skip to content

Commit

Permalink
multithreading: minor style updateS (#1504)
Browse files Browse the repository at this point in the history
Signed-off-by: Lynette Miles <[email protected]>
  • Loading branch information
esmerel authored Nov 7, 2024
1 parent 5d8a650 commit 26a9ffe
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 6 deletions.
12 changes: 6 additions & 6 deletions administration/multithreading.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,23 +6,23 @@ description: Learn how to run Fluent Bit in multiple threads for improved scalab

Fluent Bit has one event loop to handle critical operations, like managing
timers, receiving internal messages, scheduling flushes, and handling retries.
This event loop runs in Fluent Bit's main thread.
This event loop runs in the main Fluent Bit thread.

To free up resources in the main thread, you can configure
[inputs](../pipeline/inputs/README.md) and [outputs](../pipeline/outputs/README.md)
to run in their own self-contained threads. However, inputs and outputs implement
multithreading in distinct ways: inputs can run in **threaded** mode, and outputs
can use one or more **workers**.
multithreading in distinct ways: inputs can run in threaded mode, and outputs
can use one or more workers.

Threading also affects certain processes related to inputs and outputs. For example,
Threading also affects certain processes related to inputs and outputs. For example,
[filters](../pipeline/filters/README.md) always run in the main thread, but
[processors](../pipeline/processors/README.md) run in the self-contained threads of
their respective inputs or outputs, if applicable.

## Inputs

When inputs collect telemetry data, they can either perform this process
inside Fluent Bit's main thread or inside a separate dedicated thread. You can
inside the main Fluent Bit thread or inside a separate dedicated thread. You can
configure this behavior by enabling or disabling the `threaded` setting.

All inputs are capable of running in threaded mode, but certain inputs always
Expand All @@ -33,7 +33,7 @@ run in threaded mode regardless of configuration. These always-threaded inputs a
- [Process Exporter Metrics](../pipeline/inputs/process-exporter-metrics.md)
- [Windows Exporter Metrics](../pipeline/inputs/windows-exporter-metrics.md)

Inputs are not internally aware of multithreading. If an input runs in threaded
Inputs aren't internally aware of multithreading. If an input runs in threaded
mode, Fluent Bit manages the logistics of that input's thread.

## Outputs
Expand Down
1 change: 1 addition & 0 deletions vale-styles/FluentBit/Spelling-exceptions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,7 @@ matchers
Minishift
minikube
MTTx
multithreading
namespace
namespaces
Nginx
Expand Down

0 comments on commit 26a9ffe

Please sign in to comment.