You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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) .
Attempted Solutions
Proposal
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.
References
The text was updated successfully, but these errors were encountered:
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.
ghost
locked as resolved and limited conversation to collaborators
Oct 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SDK version
Master branch
Use-cases
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) .Attempted Solutions
Proposal
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.References
The text was updated successfully, but these errors were encountered: