You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CloudWatch deliberately organizes metrics into various groupings and dimensions and we report documents the way we collect them from CloudWatch (no aggregations).
If a CoudWatch metric is collected with a set of dimensions, we look for all data points with the same dimensions and then put them in one document and send them to ES.
In this case for API Gateway, there might be some confusion as to why we have 4 documents:
Upon further investigation, they are correlated to their corresponding CloudWatch metrics/dimensions groupings:
No dimensions -> Across All APIs
ApiName as a dimension -> By Api Name
ApiName, Stage as dimension -> By Stage
ApiName, Stage, Resource, Method -> By Method
A section in the documentation should explain the correspondence between CloudWatch metrics groupings and the documents. Other AWS services with similar behaviour include RedShift, DynamoDB.
The text was updated successfully, but these errors were encountered:
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
Uh oh!
There was an error while loading. Please reload this page.
CloudWatch deliberately organizes metrics into various groupings and dimensions and we report documents the way we collect them from CloudWatch (no aggregations).
If a CoudWatch metric is collected with a set of dimensions, we look for all data points with the same dimensions and then put them in one document and send them to ES.
In this case for API Gateway, there might be some confusion as to why we have 4 documents:

Upon further investigation, they are correlated to their corresponding CloudWatch metrics/dimensions groupings:
A section in the documentation should explain the correspondence between CloudWatch metrics groupings and the documents. Other AWS services with similar behaviour include RedShift, DynamoDB.
The text was updated successfully, but these errors were encountered: