Skip to content

Commit 98e4159

Browse files
committed
debugging: add detailed examples for enabling debug logging
Signed-off-by: Wesley Pettit <[email protected]>
1 parent 53d99cc commit 98e4159

File tree

1 file changed

+30
-1
lines changed

1 file changed

+30
-1
lines changed

troubleshooting/debugging.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -537,7 +537,36 @@ When you experience a problem, before you cut us an issue, try the following.
537537

538538
Many Fluent Bit problems can be easily understood once you have full log output. Also, if you want help from the aws-for-fluent-bit team, we generally request/require debug log output.
539539

540-
The log level for Fluent Bit can be set in the [Service section](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit), or by setting the env var `FLB_LOG_LEVEL=debug`.
540+
The log level for Fluent Bit can be set in the [Service section](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit), or by setting the environment variable `FLB_LOG_LEVEL=debug`.
541+
542+
For example, in the service section:
543+
```
544+
[SERVICE]
545+
Log_Level debug
546+
```
547+
548+
Remember, you can only have a single `[SERVICE]` configured across all of your configuration files for Fluent Bit.
549+
550+
Alternatively, set the log level via an environment variable. In your ECS task definition:
551+
```
552+
"environment": [
553+
{
554+
"name": "FLB_LOG_LEVEL",
555+
"value": "debug"
556+
}
557+
],
558+
```
559+
560+
In your kubernetes YAML:
561+
562+
```
563+
spec:
564+
containers:
565+
- name: fluent-bit
566+
env:
567+
- name: FLB_LOG_LEVEL
568+
value: debug
569+
```
541570

542571
#### Enabling Monitoring for Fluent Bit
543572

0 commit comments

Comments
 (0)