Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy message contents from CloudWatch Logs #2333

Closed
genachka opened this issue Jan 8, 2021 · 3 comments
Closed

Copy message contents from CloudWatch Logs #2333

genachka opened this issue Jan 8, 2021 · 3 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@genachka
Copy link

genachka commented Jan 8, 2021

Using IntelliJ IDEA 2020.3.1 and AWS Toolkit 1.22-203. When I right click on Lambda function within the AWS Explorer and select View Log Streams and then open a specific stream, it has two columns, Time and Message. It used to be that I could right click on a row and there was a copy option which used to give me just the message contents for that row. Now right click on a row only has an option for Show Logs Around. If I use keyboard shortcut to copy (Ctrl+C) I get the entire row contents.

It would be very useful to have the right click popup menu have copy put back and to be able to right click and be able to have option to copy the entire row or option for that row's cell that was clicked on. As right now I have to take extra time each time to remove the extra data copied.

@genachka genachka added the bug We can reproduce the issue and confirmed it is a bug. label Jan 8, 2021
@hunterwerlla
Copy link
Contributor

hunterwerlla commented Jan 8, 2021

Hello, you should be able to box select messages in the table and copy should only copy messages. Can you check if that works?

@abrooksv
Copy link
Contributor

abrooksv commented Jan 9, 2021

@hunterwerlla We fixed that for CFN but not CW Logs

@abrooksv
Copy link
Contributor

abrooksv commented Jan 9, 2021

Offending commit: 679faa8

Thank you for bringing this to our attention, we will get it fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

3 participants