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/inputs/tail.md
+84Lines changed: 84 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ The plugin supports the following configuration parameters:
38
38
|`File_Cache_Advise`| Set the `posix_fadvise` in `POSIX_FADV_DONTNEED` mode. This reduces the usage of the kernel file cache. This option is ignored if not running on Linux. |`On`|
39
39
|`Threaded`| Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). |`false`|
40
40
|`Unicode.Encoding`| Set the encoding which the origin of character encoding. Currently, UTF-16LE, UTF-16BE, and auto is supported. |_none_|
41
+
|`Generic.Encoding`| Set the encoding which the origin of character encoding. Currently, ShiftJIS, UHC, GBK, GB18030, Big5, Win866, Win874, Win1250, Win1251, Win1252, Win2513, Win1254, Win1255, Win1256 are supported. |_none_|
41
42
42
43
{% hint style="info" %} If the database parameter `DB` isn't
43
44
specified, by default the plugin reads each target file from the
@@ -436,3 +437,86 @@ While file rotation is handled, there are risks of potential log loss when using
436
437
- Final note: the `Path` patterns can't match the rotated files. Otherwise, the rotated file would be read again and lead to duplicate records.
437
438
438
439
{% endhint %}
440
+
441
+
## Character Encoding Conversion
442
+
443
+
This feature allows Fluent Bit to convert logs from various character encodings into the standard UTF-8 format.
444
+
This is crucial for processing logs from systems, especially Windows, that use legacy or non-UTF-8 encodings.
445
+
Proper conversion ensures that your log data is correctly parsed, indexed, and searchable.
446
+
447
+
### When to Use This Feature
448
+
449
+
You should use this feature if your log files or messages are not in UTF-8 and you are seeing garbled or incorrectly rendered characters.
450
+
This is common in environments that use:
451
+
452
+
* Modern Windows applications that log in UTF-16.
453
+
454
+
* Legacy Windows systems with applications that use traditional code pages (e.g., ShiftJIS, GBK, Win1252).
455
+
456
+
### Configuration Parameters
457
+
458
+
To enable encoding conversion, you will use one of the following two parameters within an input plugin configuration.
459
+
460
+
1.`Unicode.Encoding`
461
+
462
+
Use this parameter for high-performance conversion of UTF-16 encoded logs to UTF-8. This method utilizes modern processor features (SIMD instructions) to accelerate the conversion process, making it highly efficient.
463
+
464
+
* Use Case: Ideal for logs coming from modern Windows environments that default to UTF-16.
465
+
* Supported Values:
466
+
* UTF-16LE (Little-Endian)
467
+
* UTF-16BE (Big-Endian)
468
+
469
+
2.`Generic.Encoding`
470
+
471
+
Use this parameter to convert from a wide variety of other character encodings, particularly legacy Windows code pages.
472
+
473
+
* Use Case: Essential for logs from older systems or applications configured for specific regions, common in East Asia and Eastern Europe.
474
+
* Supported Values: You can use any of the names or aliases listed below.
0 commit comments