-
Notifications
You must be signed in to change notification settings - Fork 440
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
[AWS] [Billing] Document GetCostAndUsage API limitation #9290
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
|
||
When you want to group by a combination of several tags and dimensions, like `SERVICE` along with various tags (e.g., `team`, `project`, `aws:createdBy`), you might see duplicated data. This happens because of a [limitation](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_GetCostAndUsage.html) with the `GetCostAndUsage` API, which only allows grouping costs by two different groups. | ||
|
||
To avoid data duplication, it's recommended to group data using two groups at once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a problem in using just one member in the group?
I guess, by group you meant - one tag + one dimension / two tags / two dimensions.
It would be best to explain this a little bit more, i think
It may be best to rephrase recommended to group data using two groups at once.
. The word group
when used in two different context makes it more confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid data duplication, it's recommended to aggregate data using a combination of two attributes, which can be either: one tag and one dimension, two tags or two dimensions.
do you think this makes more sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this improves clarity.
|
💚 Build Succeeded
History
cc @gpop63 |
@gpop63 : Are we waiting for something here? |
Package aws - 2.14.1 containing this change is available at https://epr.elastic.co/search?package=aws |
Just an FYI,
This part isn't currently possible with Elastic's AWS integration. elastic/beats#38755 attempts to resolve this, but this doc changes might be confusing to users. |
* update docs * bump package version * fix PR link * clarify billing limitation
Overview
This change aims to document the limitation of the GetCostAndUsage API used by the
billing
metricset. Since it only allows grouping costs by two groups at once we can end up with duplicated data.Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots