2.31.7
This release includes:
- Fluent Bit 1.9.10
- Amazon CloudWatch Logs for Fluent Bit 1.9.2
- Amazon Kinesis Streams for Fluent Bit 1.10.1
- Amazon Kinesis Firehose for Fluent Bit 1.7.1
Compared to 2.23.6 this release adds:
- Bug - Fixed S3 Key Tag Corruption with
preserve_data_orderingoption aws-for-fluent-bit:541 fluent-bit:6933
This release includes the same fixes and features that we are working on getting accepted upstream as AWS for Fluent Bit 2.31.6.
We’ve run the new released image in our ECS load testing framework and here is the result. This testing result provides benchmarks of aws-for-fluent-bit under different input load. Learn more about the load test.
| plugin | source | 20 MB/s | 25 MB/s | 30 MB/s | |
|---|---|---|---|---|---|
| kinesis_firehose | stdstream | Log Loss | ✅ | 0%(4695) | ✅ |
| Log Duplication | ✅ | 0%(6000) | ✅ | ||
| kinesis_firehose | tcp | Log Loss | ✅ | ✅ | 0%(672) |
| Log Duplication | ✅ | 0%(4500) | 0%(26896) | ||
| kinesis_streams | stdstream | Log Loss | ✅ | ✅ | ✅ |
| Log Duplication | 0%(500) | 0%(7490) | 0%(1986) | ||
| kinesis_streams | tcp | Log Loss | ✅ | ✅ | ✅ |
| Log Duplication | ✅ | ✅ | 0%(25960) | ||
| s3 | stdstream | Log Loss | ✅ | ✅ | ✅ |
| Log Duplication | ✅ | ✅ | ✅ | ||
| s3 | tcp | Log Loss | ✅ | ✅ | ✅ |
| Log Duplication | ✅ | ✅ | ✅ |
| plugin | source | 1 MB/s | 2 MB/s | 3 MB/s | |
|---|---|---|---|---|---|
| cloudwatch_logs | stdstream | Log Loss | ✅ | ✅ | ✅ |
| Log Duplication | ✅ | ✅ | ✅ | ||
| cloudwatch_logs | tcp | Log Loss | ✅ | 8%(102321) | 2%(49719) |
| Log Duplication | ✅ | ✅ | ✅ |
Note:
- The green check ✅ in the table means no log loss or no log duplication.
- Number in parentheses means the number of records out of total records. For example, 0%(1064/1.8M) under 30Mb/s throughput means 1064 duplicate records out of 18M input records by which log duplication percentage is 0%.
- Log loss is the percentage of data lost and log duplication is the percentage of duplicate logs received at the destination. Your results may differ because they can be influenced by many factors like different configs and environment settings. Log duplication is exclusively caused by partially succeeded batches that were retried, which means it is random.