How To
Steps
Introduction
When troubleshooting logging issues in Terraform Enterprise, it may be necessary to temporarily increase the log verbosity of the fluent-bit container. This guide provides the procedure to set the log level to debug.
Prerequisites
- Root or
sudoaccess to the Terraform Enterprise host machine. - Terraform Enterprise installed via a Docker-based method.
Procedure
Follow these steps to modify the Fluent Bit configuration and enable debug logging.
-
Copy the
fluent-bit.conffile from thetfe-fluent-bitcontainer to the local filesystem on the host machine.# sudo docker cp tfe-fluent-bit:/fluent-bit/etc/fluent-bit.conf ./
-
Edit the local copy of
fluent-bit.confto add theLog_Levelparameter with a value ofdebugunder the[SERVICE]section.[SERVICE] Parsers_File /fluent-bit/etc/parsers.conf HTTP_Server On HTTP_Listen 0.0.0.0 HTTP_Port 2020 Health_Check On storage.path /fluent-bit/run/buffer storage.metrics on Log_Level debug -
Copy the modified configuration file back into the container, placing it in a temporary directory.
# sudo docker cp fluent-bit.conf tfe-fluent-bit:/tmp/fluent-bit.conf
-
Execute a command inside the container to move the new configuration file to its correct location, overwriting the original file.
# sudo docker exec -it tfe-fluent-bit cp /tmp/fluent-bit.conf /fluent-bit/etc/fluent-bit.conf
-
Restart the
tfe-fluent-bitcontainer to apply the new configuration.# sudo docker restart tfe-fluent-bit
Verification
Confirm that the container has restarted with debug logging enabled by checking its logs.
# sudo docker logs tfe-fluent-bit
The log output should now include more verbose entries, indicating that the debug log level is active.
Note: After you have completed troubleshooting, we recommend reverting these changes to restore the default log level and reduce log volume.
Document Location
Worldwide
Historical Number
6150988057747
Was this topic helpful?
Document Information
Modified date:
16 March 2026
UID
ibm17265057