zsmerritt / flutter_aws_cloudwatch Goto Github PK

Currently large messages can either be split or throw an error. This is probably not the best option because this large message error might only be discovered in production with real users. Instead an enum should be added that would indicate which option is preferred. Values of this enum that I can think of are [error, ignore, truncate, split].

due to removal of nullsafe args i cannot build the 1.7.0 version of the plugin

Is it possible to update the docs with an example of specifying temporary credential access?

Whenever I try to make a log request to CloudWatch using flutter web client, the first request is successfully logged to the cloudwatch as no sequence token is required for new log stream.

However, any subsequent log request to same logStream throws an error CloudWatchException - message: null.

So I tried to debug the things and found out that only statusCode value is available on web and all the other fields remains null as in below AwsResponse class.

class AwsResponse{
  int statusCode;
  String? type;
  String? message;
  String? nextSequenceToken;
  String? expectedSequenceToken;
  String? raw;
}

Sample Response on web

{
"statusCode" : 400,
"type" : null,
"message" : null,
"nextSequenceToken" : null,
"expectedSequenceToken" : null,
"raw" : null
}

Due to this the nextSequenceToken is null and on next request we get a statusCode as 400 which implies nextSequenceToken was not included in the request, and now the error handler _handleError is unable to resolve the error response as expectedSequenceToken is also null.

Hence, only single request is sent to the cloudwatch and other logs doesn't append to the same logStream.

Could you please have a look into the issue, I am trying to figure out if it's an issue with AwsRequest or universal_io.

Your thoughts would be really helpful on this.

In Flutter version 3.22.0 intl is pinned to version 0.19.0 by flutter_localizations from the flutter SDK, so aws_cloudwatch doesn't match this requirement.

Thanks.

Utilizing the region 'us-east-1' i receive the error:

{__type: InvalidSignatureException, message: Credential should be scoped to a valid region, not 'us-west-2'. }

But when utilizing the 'us-west-2' region i got this error (as expected)

{__type: ResourceNotFoundException, message: The specified log group does not exist.}

Hi,

Whenever I am trying to log some message to AWS Cloudwatch using our temp access key & secret key, the following error is thrown.

CloudWatchException - type: UnrecognizedClientException, message: The security token included in the request is invalid.

Also, could you please highlight, why the library doesn't have accessToken as a param, and how does it log without token?

I am using the latest version of the library: aws_cloudwatch: ^0.4.5

I have followed the guide as per the Example 3, as in installation guide, still encountering the issue as mentioned.

Your help would be highly appreciated.

Thanks!

@Zsmerritt

I am trying to log to an existing stream. But it is throwing CloudWatchException - type: ResourceAlreadyExistsException, message: The specified log stream already exists error.