I was spending some time debugging a performance issue with the TF Okta provider. As part of this exercise, I set the log TF_LOG level to trace. Through this code, we get nice output for request/response. Unfortunately, as far as I can tell there is no way to correlate a request with a given response in this http.RoundTripper implementation (especially in the IsDebugOrHigher branch) .
It would be nice to be able to add enough information to correlate a request/response pair. This could be as simple as adding a UUID that would be printed when IsDebugOrHigher for both the request and response output. I'm happy to submit the change if appropriate!
Alternatively, it would be really nice if we can start instrumenting terraform and providers with opentelemetry.
The text was updated successfully, but these errors were encountered:
terraform-plugin-sdk version 2.20.0 now includes a terraform-plugin-log based http.Transport that includes a unique identifier for each HTTP transaction in the tf_http_trans_id structured logging field.
I'm going to lock this issue because it has been closed for 30 days⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.