camitz / aws-cloudwatch-statsd-backend Goto Github PK

This might be related to #7

We see this in statsd.log - perhaps packing metrics might help?

Err : { StatusCode: 400,
  Headers:
   { 'x-amzn-requestid': '43732e6e-4618-11e6-9498-bf6b383bb542',
     'content-type': 'text/xml',
     'content-length': '261',
     date: 'Sat, 09 Jul 2016 21:01:10 GMT' },
  Body:
   { ErrorResponse:
      { '@': { xmlns: 'http://monitoring.amazonaws.com/doc/2010-08-01/' },
        Error:
         { Type: 'Sender',
           Code: 'Throttling',
           Message: 'Rate exceeded' },
        RequestId: '43732e6e-4618-11e6-9498-bf6b383bb542' } } }

Bumping up default statsd flushInterval to 20, 30 s does not seem to help

as above

Please update these if you think they are helpful :)

putMetricData() method allows to pack up to 40 KB of metrics. In case of producing huge number of them packing metrics in single requests could give 10-20x costs reduction.

Hi, I am following your docs for running with the most basic configuration described in your readme but am unable to send metrics to cloudwatch:

Err : { StatusCode: 403,
  Headers:
   { 'x-amzn-requestid': '-',
     'content-type': 'text/xml',
     'content-length': '311',
     date: 'Tue, 03 Jan 2017 19:03:25 GMT' },
  Body:
   { ErrorResponse:
      { '@': { xmlns: 'http://monitoring.amazonaws.com/doc/2010-08-01/' },
        Error:
         { Type: 'Sender',
           Code: 'InvalidClientTokenId',
           Message: 'The security token included in the request is invalid' },
        RequestId: '-' } } }

I am able to get statsD metrics publishing to the console backend and have verified that my access key/secret key are correct by describing cloudwatch using AWS cli:

aws cloudwatch describe-alarms

(works)

Although this repository has been updated to use the aws-sdk node package rather than awssum, the documentation is still tuned to awssum. This led me to have an error when I provided the region as "US_EAST_1" rather than "us-east-1".

Please update the documentation prior to making a more recent release.

Currently it is required to specify accessKeyId and secretAccessKey. It would be great if this backend could utilize IAM roles for authentication when running on EC2.

For more info see: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html

The region option has been changed inside code or something. When I checked the code the region option they were expecting was in the format AP_SOUTH_1, AP_SOUTHEAST_1 instead of ap-south-1, ap-southeast-1. And inside the doc its given as latter but in code they are expecting former.