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

Incorrect default rate limit on CloudWatch input #2298

Closed
cosmopetrich opened this issue Jan 23, 2017 · 1 comment
Closed

Incorrect default rate limit on CloudWatch input #2298

cosmopetrich opened this issue Jan 23, 2017 · 1 comment

Comments

@cosmopetrich
Copy link

cosmopetrich commented Jan 23, 2017

Bug report

The documentation for the CloudWatch input notes that:

Maximum requests per second. Note that the global default AWS rate limit is
10 reqs/sec, so if you define multiple namespaces, these should add up to a
maximum of 10. Optional - default value is 10.

Is this actually correct? The AWS service limits documentation describes the following limits.

GetMetricStatistics - 400 transactions per second (TPS)
ListMetrics - 25 transactions per second (TPS)

The page linked in a comment shows the same limits. I can't find any information on a specific global rate other than a note that there's a vague per-region rate. Where did the figure of 10 come from? Is it possible that there was some confusion with the GetLogEvents limit, which was 10 at the time the rate limit feature was added?

@sparrc
Copy link
Contributor

sparrc commented Jan 23, 2017

that could be, it's possible that AWS increased their limits.

If you want to change this please just submit a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants