Support readiness

To ensure smooth communication and efficient support, follow these guidelines.

Each team member has an account created through our support portal.
Configure each team member permitted to create support tickets on behalf of your company as an Authorized Technical Contact in the support portal. Please provide a list of applicable team members to your company's assigned Solutions Engineer so that they can configure this.
Have your team familiarize themselves with our documentation(opens in new tab) on how to open a support ticket with HashiCorp Support and generate/upload a support bundle, whenever applicable.
Be aware of the support plan level your company has purchased to manage expectations of response times. Also, understand the definitions for each severity level when opening a support ticket through our documentation(opens in new tab).

Capturing command-line trace logs

For issues related to Terraform command-line behavior — whether running locally or in a command-line-driven workflow — collect a trace log before opening a support ticket. Providing trace output up front reduces time-to-triage and helps HashiCorp Support identify the root cause without additional back-and-forth. See the HashiCorp Support KB on enabling trace-level logs(opens in new tab) for additional context.

Enable trace logging

Set TF_LOG and, optionally, TF_LOG_PATH before running the affected Terraform command:

export TF_LOG=TRACE
export TF_LOG_PATH=./terraform.log
terraform plan

Setting TF_LOG_PATH directs Terraform to append all log output to the specified file. You must also set TF_LOG — TF_LOG_PATH alone does not activate logging.

To set TF_LOG for a single command without modifying your shell session permanently, use an inline variable assignment and pipe all output to a file:

TF_LOG=TRACE terraform plan -no-color 2>&1 | tee plan.log

Use -no-color to keep log output readable and safe for upload to a support ticket.

Narrow log scope

To limit verbosity to a specific subsystem, use TF_LOG_CORE or TF_LOG_PROVIDER in place of, or alongside, TF_LOG. Both accept the same level values (TRACE, DEBUG, INFO, WARN, ERROR):

Use TF_LOG_CORE=TRACE when the issue appears to originate in the Terraform planning or state layer.
Use TF_LOG_PROVIDER=TRACE when the issue appears to originate in provider calls or resource lifecycle operations.

Clean up after troubleshooting

Unset the log variables after each troubleshooting session to avoid accumulating verbose output in subsequent runs:

unset TF_LOG TF_LOG_PATH TF_LOG_CORE TF_LOG_PROVIDER

For full details on available log levels and configuration, refer to the Terraform debugging documentation(opens in new tab) and the environment variables reference(opens in new tab).

Note

Trace logs capture Terraform command-line behavior and are appropriate for issues seen in local runs and command-line-driven workflows. For Terraform Enterprise platform issues — such as worker failures, application errors, or storage layer problems — use the diagnostics and support bundle workflow(opens in new tab) covered in the support ticket guidance in the preceding section.

Observability

Changelog