-
Notifications
You must be signed in to change notification settings - Fork 94
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
[COST-4741] - Separate AWS node network costs into a Network unattributed namespace #5104
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ceae5a5
AWS network costs
samdoran 182501f
Separate node network costs into a Network unattributed project
samdoran c3cc6c6
Lower case string for comparison
samdoran 1cc6a8f
Fix comparison and add data_transfer_direction to final table
samdoran a30e075
Populate data transfer amounts
samdoran 0cd41d6
No need to aggregate on the field that is being grouped by
samdoran 0f69050
Use strpos instead of position
samdoran 6422e4d
Group by lineitem_usagetype
samdoran daae1e0
Only use Pod data source for Network unattributed costs
samdoran c9d314e
Group by lineitem_operation in order to determine correct direction
samdoran ff66962
Set data value to NULL for non-applicable direction
samdoran 1db894e
Merge branch 'main' into COST-3761/COST-4741-aws-network-costs
samdoran File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This SQL is grouped by these items below, are these enough to ensure a unique
data_transfer_direction
or should we be grouping by thedata_transfer_direction
result as well?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.
We do probably need to group by the direction, but we can't use an aggregation in a group by. Grouping by
aws.lineitem_usagetype
may work.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.
You can also use numbers to group by items in the
SELECT
statement, for example the4
in the group by there is based on theCASE
statement in the SQL