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
AWSCloudWatchProvider fails to log to a brand-new log stream #9050
Comments
Hi @ibliskavka 👋 thanks for raising this issue! Since you provided the correction for the line of code, would you like to submit a Pull Request for the team to review? |
Hi 👋 Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you. Thank you! |
Why was this issue closed? The steps that were originally posted look correct in how to reproduce the problem. I ran into this issue this morning and there looks to be others posting about it under the original feature PR. When writing to an empty log-stream for the first time then all writes will fail because I'd be happy to post a PR. |
Same here! When trying to follow instructions in #8309 to get Amplify to send logs to Cloudwatch, at first I was unable to because of exactly same error - sequence token. |
Thanks for the merge. I checked out |
it is also in |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Not applicable
Amplify Categories
Not applicable
Environment information
Put output below this line
System:
OS: Linux 5.10 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Memory: 9.66 GB / 12.33 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.17.5 - /usr/bin/node
Yarn: 1.22.11 - /mnt/c/Users/iblis/AppData/Roaming/npm/yarn
npm: 6.14.14 - /usr/bin/npm
npmGlobalPackages:
aws-cdk: 1.122.0
npm: 6.14.14
Describe the bug
AWSCloudWatchProvider (
packages/core/src/Providers/AWSCloudWatchProvider.ts
) throws the following errors when sending logs to a brand new stream.API Response
When I call the CloudWatch API directly without a token to initialize the first stream message, the provider works.
Expected behavior
AWSCloudWatchProvider
shouldn't be initializing_nextSequenceToken
to empty string. The value should be undefined.Original Line: 379
this._nextSequenceToken = logStream.uploadSequenceToken || '';
Requested Changes:
this._nextSequenceToken = logStream.uploadSequenceToken || undefined;
Reproduction steps
AWSCloudWatchProvider
with a non-existing stream nameCode Snippet
Log output
Log Output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: