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
Copy file name to clipboardExpand all lines: pipeline/outputs/syslog.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ You must be aware of the structure of your original record so you can configure
31
31
| syslog\_sd\_key | The key name from the original record that contains a map of key/value pairs to use as Structured Data \(SD\) content. The key name is included in the resulting SD field as shown in examples below. This configuration is optional. ||
32
32
| syslog\_message\_key | The key name from the original record that contains the message to deliver. Note that this property is **mandatory**, otherwise the message will be empty. ||
33
33
| allow\_longer\_sd\_id| If true, Fluent-bit allows SD-ID that is longer than 32 characters. Such long SD-ID violates RFC 5424.| false |
34
+
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. |`0`|
34
35
35
36
### TLS / SSL
36
37
@@ -123,7 +124,7 @@ Example configuration file:
123
124
syslog_hostname_key hostname
124
125
syslog_appname_key appname
125
126
syslog_procid_key procid
126
-
syslog_msgid_key msgid
127
+
syslog_msgid_key msgid
127
128
syslog_sd_key uls@0
128
129
syslog_message_key log
129
130
```
@@ -156,19 +157,19 @@ Example output:
156
157
157
158
### Adding Structured Data Authentication Token
158
159
159
-
Some services use the structured data field to pass authentication tokens (e.g. `[<token>@41018]`), which would need to be added to each log message dynamically.
160
-
However, this requires setting the token as a key rather than as a value.
160
+
Some services use the structured data field to pass authentication tokens (e.g. `[<token>@41018]`), which would need to be added to each log message dynamically.
161
+
However, this requires setting the token as a key rather than as a value.
161
162
Here's an example of how that might be achieved, using `AUTH_TOKEN` as a [variable](../../administration/configuring-fluent-bit/classic-mode/variables.md):
162
163
163
164
{% tabs %}
164
165
{% tab title="fluent-bit.conf" %}
165
166
```text
166
-
[FILTER]
167
+
[FILTER]
167
168
name lua
168
169
match *
169
170
call append_token
170
171
code function append_token(tag, timestamp, record) record["${AUTH_TOKEN}"] = {} return 2, timestamp, record end
171
-
172
+
172
173
[OUTPUT]
173
174
name syslog
174
175
match *
@@ -213,4 +214,4 @@ Here's an example of how that might be achieved, using `AUTH_TOKEN` as a [variab
0 commit comments