-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Cloudwatch plugin needs some throttling #1197
Comments
can this not be controlled by using the |
Sadly, no: If I'm reading this correctly, this will create 64 concurrent requests to AWS. Additionally, there is no delay in executing subsequent requests. |
Hey! I'm still getting throttling from AWS even with version 1.0.0-beta3, is there a config I need to add to enable this? |
there isn't, it should be doing it automatically, but we might want to add a config option for how many requests per second to limit it to |
Considering that the API rate limit for GetMetricStatistics can be raised (ie: I might want that throttle higher) and I might have other tools querying metrics against the account (ie: I might want that throttle lower), feels correct that the requests per second cap should be a config option. Relatedly, if I define multiple inputs.cloudwatch sections, is the throttle global for all of Telegraf or per input/namespace? |
@tmonk42 it's per input |
I'm getting API throttling from AWS when I'm using cloudwatch plugin. It would be nice to have some throttling. AWS has guidelines here: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/cloudwatch_limits.html
The text was updated successfully, but these errors were encountered: