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
Even though we now could filter the data by CloudAccountID, now when querying the data for "sum" in the 60s interval, Kibana would report double the value that shows up on Cloud watch. Looking closer at the documents we found that the documents are coming through duplicated except for one field "aws.dimensions.TransitGatewayAttachment", where one document has a value, and another document doesn't. ( We created a work-around to get the value deduplicated by adding a filter of type aws.dimensions.TransitGatewayAttachment : *. )
All fields match except aws.dimensions.TransitGatewayAttachment, and this is happening with almost all documents, I did catch a few where it didn't, but they were very few of them.
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!
AWS Cloudwatch v8.6.2
Even though we now could filter the data by CloudAccountID, now when querying the data for "sum" in the 60s interval, Kibana would report double the value that shows up on Cloud watch. Looking closer at the documents we found that the documents are coming through duplicated except for one field "aws.dimensions.TransitGatewayAttachment", where one document has a value, and another document doesn't. ( We created a work-around to get the value deduplicated by adding a filter of type
aws.dimensions.TransitGatewayAttachment : *
. )All fields match except
aws.dimensions.TransitGatewayAttachment
, and this is happening with almost all documents, I did catch a few where it didn't, but they were very few of them.The text was updated successfully, but these errors were encountered: