Skip to content

Admin/config/upstream updates for style #1649

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

Merged
merged 2 commits into from
May 13, 2025
Merged

Admin/config/upstream updates for style #1649

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
114d3a7
Admin/config/upstream updates for style
esmerel May 13, 2025
39aca31
Update administration/configuring-fluent-bit/yaml/upstream-servers-se…
esmerel May 13, 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
20 changes: 8 additions & 12 deletions administration/configuring-fluent-bit/yaml/upstream-servers-section.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
# Upstream Servers Section
# Upstream servers

The `Upstream Servers` section defines a group of endpoints, referred to as nodes, which are used by output plugins to distribute data in a round-robin fashion. This is particularly useful for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](https://docs.fluentbit.io/manual/pipeline/outputs/forward) and [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch).
The `upstream_servers` section defines a group of endpoints, referred to as nodes. Nodes are used by output plugins to distribute data in a round-robin fashion. This is useful for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](https://docs.fluentbit.io/manual/pipeline/outputs/forward) and [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch).

In YAML, this section is named `upstream_servers` and requires specifying a `name` for the group and a list of `nodes`. Below is an example that defines two upstream server groups: `forward-balancing` and `forward-balancing-2`:
The `upstream_servers` section require specifying a `name` for the group and a list
of `nodes`. The following example defines two upstream server groups, `forward-balancing` and `forward-balancing-2`:

```yaml
upstream_servers:
Expand Down Expand Up @@ -34,13 +35,8 @@ upstream_servers:
port: 51000
```

### Key Concepts
Each node in the `upstream_servers` group must specify a `name`, `host`, and `port`.
Additional settings like `tls`, `tls_verify`, and `shared_key` can be configured for
secure communication.

- Nodes: Each node in the upstream_servers group must specify a name, host, and port. Additional settings like tls, tls_verify, and shared_key can be configured as needed for secure communication.


### Usage Note

While the `upstream_servers` section can be defined globally, some output plugins may require the configuration to be specified in a separate YAML file. Be sure to consult the documentation for each specific output plugin to understand its requirements.

For more details, refer to the documentation of the respective output plugins.
While the `upstream_servers` section can be defined globally, some output plugins might require the configuration to be specified in a separate YAML file. Consult the documentation for each specific output plugin to understand its requirements.