You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Upstream Servers configuration uses YAML format, then it can be placed in the same file as main configuration (e.g. in fluent-bit.yaml), like:
231
+
232
+
```yaml
233
+
pipeline:
234
+
inputs:
235
+
- name: dummy
236
+
dummy: "{ \"message\" : \"this is dummy data\" }"
237
+
outputs:
238
+
- name: es
239
+
match: *
240
+
index: fluent-bit
241
+
type: my_type
242
+
upstream: ./fluent-bit.yaml
243
+
upstream_servers:
244
+
- name: es-balancing
245
+
nodes:
246
+
- name: node-1
247
+
host: localhost
248
+
port: 9201
249
+
- name: node-2
250
+
host: localhost
251
+
port: 9202
252
+
- name: node-3
253
+
host: localhost
254
+
port: 9203
255
+
```
256
+
207
257
## Elasticsearch field names
208
258
209
259
Some input plugins can generate messages where the field names contains dots (`.`). For Elasticsearch 2.0, this isn't allowed. The current `es` plugin replaces
0 commit comments