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

"View Full Log Stream" repeatedly timing-out? #6605

Open
ModalityZ opened this issue Feb 18, 2025 · 4 comments
Open

"View Full Log Stream" repeatedly timing-out? #6605

ModalityZ opened this issue Feb 18, 2025 · 4 comments
Labels
guidance General information and guidance, answers to FAQs, or recommended best practices/resources. partner-team Triggers issue routing to owner team performance service:cloudwatch ux user experience

Comments

@ModalityZ
Copy link

System details (run AWS: About and/or Amazon Q: About)

  • OS: Linux x64 6.8.0-53-generic
  • Visual Studio Code version: 1.97.2
  • AWS Toolkit version: 3.46.0
  • Amazon Q version: N/A

Question

I just discovered "View Full Log Stream" after years of being frustrated that I have to request page after page of CW Log results. But both times that I've tried it, it times out.

FWIW, My .aws/credentials uses credential_process which in turn uses op, the 1Password shell plugin, so I can avoid having unencrypted credentials on-disk.

How can I avoid these timeouts?

2025-02-18 09:28:23.021 [info] Log level: info, beta=false
2025-02-18 09:28:23.021 [info] endpoints: retrieving AWS endpoints data
2025-02-18 09:28:23.021 [info] Telemetry product: AWS Toolkit For VS Code
2025-02-18 09:28:23.285 [info] Telemetry clientId: ec85fada-7876-4528-9a79-8c0ab13bd8bb
2025-02-18 09:28:23.286 [info] Telemetry sessionId: 42d8eab3-3236-41e2-8c2a-d35028b93ff9
2025-02-18 09:28:23.956 [warning] AwsContext: no default region in credentials profile, falling back to us-east-1:
2025-02-18 09:28:25.172 [info] OS: Linux x64 6.8.0-53-generic
2025-02-18 09:28:25.172 [info] Visual Studio Code extension host: 1.97.2
2025-02-18 09:28:25.172 [info] AWS Toolkit: 3.46.0
2025-02-18 09:28:25.172 [info] node: 20.18.1
2025-02-18 09:28:25.172 [info] electron: 32.2.7
2025-02-18 09:28:25.182 [info] initialized 'submitFeedback' command with default feedback id: AWS Toolkit
2025-02-18 09:28:25.213 [info] auth: Updating connection state of profile:default to authenticating
2025-02-18 09:28:40.359 [info] auth: Updating connection state of profile:default to valid
2025-02-18 09:28:40.898 [warning] Ec2MetadataClient failed to fetch token. If this is an EC2 environment, then Toolkit will fall back to IMDSv1: TimeoutError: Socket timed out without establishing a connection ()
2025-02-18 09:28:41.871 [warning] command failed (not registered?): "aws.amazonq.refreshConnectionCallback"
2025-02-18 09:31:32.564 [error] aws.loadLogStreamFile: Error: Timeout token expired
2025-02-18 09:32:40.987 [error] aws.addLogEvents: TypeError: (0 , m.localize) is not a function
2025-02-18 09:33:24.258 [info] telemetry: sent batch (size=18)
2025-02-18 09:34:57.197 [error] aws.loadLogStreamFile: Error: Timeout token expired

@ModalityZ ModalityZ added the guidance General information and guidance, answers to FAQs, or recommended best practices/resources. label Feb 18, 2025
@ModalityZ ModalityZ changed the title How to avoid "View Full Log Stream" repeatedly times-out? How to avoid "View Full Log Stream" repeatedly timing-out? Feb 18, 2025
@jpinkney-aws jpinkney-aws added service:cloudwatch partner-team Triggers issue routing to owner team labels Feb 18, 2025
@justinmk3
Copy link
Contributor

Relevant log message:

aws.loadLogStreamFile: Error: Timeout token expired

If the log stream is very large, View Full Log Stream may not be prepared to handle requests that take minutes. We'll need to see if there is a way of handling this better.

As a workaround, does AWS: Search Log Group help?

@justinmk3 justinmk3 added ux user experience performance labels Feb 18, 2025
@justinmk3 justinmk3 changed the title How to avoid "View Full Log Stream" repeatedly timing-out? "View Full Log Stream" repeatedly timing-out? Feb 18, 2025
@ModalityZ
Copy link
Author

We'll need to see if there is a way of handling this better.

Thanks.

As a workaround, does AWS: Search Log Group help?

I haven't used it (I suppose it's under the Command Palette). But I need a few hundred log lines around a timestamp that might be weeks old. Is there a way to jump to such a snippet?

@justinmk3
Copy link
Contributor

Yes, AWS: Search Log Group supports date ranges and other filters.

@ModalityZ
Copy link
Author

Yes, AWS: Search Log Group supports date ranges and other filters.

That's great. Making it easier to find as an option under the magnifier-glass button in the extension would be even better. I see only date range there, not timestamp range. I spend hours waiting to click "Load newer events".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance General information and guidance, answers to FAQs, or recommended best practices/resources. partner-team Triggers issue routing to owner team performance service:cloudwatch ux user experience
Projects
None yet
Development

No branches or pull requests

3 participants