-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Bug Report
Describe the bug
When I am trying to test my output HTTP plugin in failure scenario (moderate load) I saw following error fluent-bit log:
[2020/04/24 18:25:09] [ warn] [engine] failed to flush chunk '1-1587752693.632712160.flb', retry in 64 seconds: task_id=726, input=tail.0 > output=http.0
[2020/04/24 18:25:11] [ warn] [engine] failed to flush chunk '1-1587752691.241037672.flb', retry in 34 seconds: task_id=695, input=tail.0 > output=http.0
[2020/04/24 18:25:11] [error] [out_http] hostname.domain.com:443, HTTP status=400
I am using fluent-bit 1.3.11 container in kubernetes
To Reproduce
- Rubular link if applicable:
- Example log message if applicable:
Sample 1:
log="2020-04-24T18:34:21.732404578Z stdout F 57.169.194.71 - - [24/Apr/2020:18:34:21 +0000] "GET /amplicative HTTP/1.0" 204 2216"
Sample 2:
log="2020-04-24T18:35:07.862616565Z stdout F 2020-04-24T18:35:07+0000 WARN A warning that should be ignored is usually at this level and should be actionable."
Sample 3:
log="2020-04-24T18:35:28.969774421Z stdout F {"@timestamp": "2020-04-24T18:35:28+0000", "level": "INFO", "message": "takes the value and converts it to string."}"
- Steps to reproduce the problem:
Expected behavior
Screenshots
Your Environment
- Version used:1.3.11
- Configuration: Kubernetes
- Environment name and version (e.g. Kubernetes? What version?): Kubernetes v1.14.10
- Server type and version:
- Operating System and version: Ubuntu 18.04.4 LTS
- Filters and plugins: Kubernetes in and http out plugin with record_modifier, nest/list, modify
Additional context
@edsiper Could please elaborate the failure mechanism of fluent-bit, it will be really helpful for me.