Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[COST-4741] - Separate AWS node network costs into a Network unattributed namespace #5104

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

[COST-4741] - Separate AWS node network costs into a Network unattributed namespace #5104

wants to merge 10 commits into from

Commits on Jun 20, 2024

  1. Add UsageType and Operation to daily data

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    bb5f7a2 View commit details
    Browse the repository at this point in the history

  2. AWS network costs 

    - Add data transfer direction to daily summary
- Separate node network costs out into network unattributed
    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    584fe2f View commit details
    Browse the repository at this point in the history

  3. Separate node network costs into a Network unattributed project

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    26b2d5c View commit details
    Browse the repository at this point in the history

  4. Lower case string for comparison

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    85c76f5 View commit details
    Browse the repository at this point in the history

  5. Fix comparison and add data_transfer_direction to final table

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    37387c0 View commit details
    Browse the repository at this point in the history

  6. Populate data transfer amounts

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    dc47964 View commit details
    Browse the repository at this point in the history

  7. Update test

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    4c61dc7 View commit details
    Browse the repository at this point in the history

  8. No need to aggregate on the field that is being grouped by

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    af1beb1 View commit details
    Browse the repository at this point in the history

  9. Use strpos instead of position

    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    7949678 View commit details
    Browse the repository at this point in the history

  10. Group by lineitem_usagetype 

    It’s not possible to use an aggregation in a GROUP BY statement, so grouping by
the lineitem_usagetype is the closest I could think of. It may result in too
many distinct rows, though.
    @samdoran
    samdoran committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    5f78bed View commit details
    Browse the repository at this point in the history