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
Use the String representation instead of the standard int64 (nanoseconds) output.
What problem does this solve?
When turning on these logs and eyeballing them to see if there are latency issues between the agent(s) and the proxies, having the string representation which includes a unit and tries to choose the most appropriate unit for you, assists in the interpretation.
What would you like Teleport to do?
In the debug log generated by https://github.com/gravitational/teleport/blob/1ff524df8d433b3cf8cc5b07acde7350ad4f3a42/lib/reversetunnel/localsite.go#L775C1-L776C1:
Use the
String
representation instead of the standardint64
(nanoseconds) output.What problem does this solve?
When turning on these logs and eyeballing them to see if there are latency issues between the agent(s) and the proxies, having the string representation which includes a unit and tries to choose the most appropriate unit for you, assists in the interpretation.
See: https://pkg.go.dev/time#Duration.String
Instead of:
It would be:
The text was updated successfully, but these errors were encountered: