Filter by empty aws.dimensions.TransitGatewayAttachment in transitgat…#5499
Filter by empty aws.dimensions.TransitGatewayAttachment in transitgat…#5499francescayeye wants to merge 2 commits intoelastic:mainfrom
Conversation
🌐 Coverage report
|
drewdaemon
left a comment
There was a problem hiding this comment.
Change make sense to me!
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
|
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
…eway dashboard
Bug
What does this PR do?
Transitgateway metrics are reported with two dimensions:
aws.dimensions.TransitGatewayaws.dimensions.TransitGatewayAttachmentThe sum of the metrics with the same
aws.dimensions.TransitGatewayvalue and differentaws.dimensions.TransitGatewayAttachmentvalues is equal to the value of the metrics with the sameaws.dimensions.TransitGatewayvalue only and emptyaws.dimensions.TransitGatewayAttachment.The dashboard for the integration shows stats at
aws.dimensions.TransitGatewaylevel, and not ataws.dimensions.TransitGatewayAttachment. Therefore we have to filter by emptyaws.dimensions.TransitGatewayAttachmentvalues, so that the values showed in the dashboard are not doubled respect their reality.Checklist
- [ ] I have verified that all data streams collect metrics or logs.changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots