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
In order to get more visibility into the request lifecycle it would be nice if there were traces, at least at the top-level methods. We make a lot of requests using this SDK and currently use a TracingClientWrapper, but it would be nice if tracing were built-in.
New or Affected Resource(s)
Most, if not all, resources.
Provide a documentation link
No response
Additional Information?
Ideally, this would just involve adding a couple of lines to top-level methods. For example, add
Describe the feature request?
In order to get more visibility into the request lifecycle it would be nice if there were traces, at least at the top-level methods. We make a lot of requests using this SDK and currently use a
TracingClientWrapper
, but it would be nice if tracing were built-in.New or Affected Resource(s)
Most, if not all, resources.
Provide a documentation link
No response
Additional Information?
Ideally, this would just involve adding a couple of lines to top-level methods. For example, add
to
okta/okta.go
and then, e.g., inokta/user.go
the use of this tracer would look something like:I'm happy to create a PR if you think this is something that you wish to add.
Thank you!
The text was updated successfully, but these errors were encountered: