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
When I access a log tail, I am usually looking to copy some of it and put it into an editor so i'm not "chasing the tail". I think this is typical, expected use.
Expected behaviors:
I expect to be able to ctrl-A (or similar with context menu or buttons) in the log widow and get the full (loaded in memory) text of the log, instead of a bunch of junk UI text and the small part of the log that's visible in viewport.
Then I'd expect to be able to use ctrl-C (or context menu/UI buttons) to copy my full selection to clipboard. Not just what's visible in viewport.
Related UX notes:
Download > "Visible Logs" / "All logs" seem like semifunctional placeholders for the above, more usual, behavior
"Visible Logs" doesn't have a specific clear meaning since that could be what's visible in the window or the range of logs that are loaded in a tail. I have no idea what these buttons do until I experiment (and then I'm disappointed because it's not actually very helpful, given how key logs are to devops and debugging)
The text was updated successfully, but these errors were encountered:
When I access a log tail, I am usually looking to copy some of it and put it into an editor so i'm not "chasing the tail". I think this is typical, expected use.
Expected behaviors:
Related UX notes:
The text was updated successfully, but these errors were encountered: