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.

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

Prefer rollup records with tags to grouping in chargeback #21059

Conversation

lpichler
Copy link
Contributor

This is applicable only for tag group feature in chargeback reports.

Each group on result report is calculated with all metric rollups in the consumptions.
But it is possible that all metric rollups don't have tag names in whole consumptions.
For example: When Vm was untagged in middle of month then we need to reflect it in chargeback calculation for each group on report result and we should use only metric rollups with tag name (in MetricRollup#tag_names)

When we have resource tagged - this is no applied. We use all metric rollups of resource in the consumption.

@miq-bot assign @gtanzillo

@miq-bot add_label bug, chargeback

@miq-bot
Copy link
Member

miq-bot commented Feb 17, 2021

@lpichler Cannot apply the following label because they are not recognized:

  • chargeback

All labels for ManageIQ/manageiq: https://github.com/ManageIQ/manageiq/labels

@miq-bot miq-bot added the bug label Feb 17, 2021
@lpichler lpichler force-pushed the prefer_rollups_tags_to_grouping_in_chargeback branch from 0d92b66 to 308f884 Compare February 22, 2021 13:45
@lpichler lpichler force-pushed the prefer_rollups_tags_to_grouping_in_chargeback branch from 308f884 to 8bf9fec Compare February 22, 2021 14:04
@miq-bot
Copy link
Member

miq-bot commented Feb 22, 2021

Checked commits lpichler/manageiq@dba8cd1~...8bf9fec with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint
4 files checked, 1 offense detected

app/models/chargeback/consumption_with_rollups.rb

@gtanzillo gtanzillo merged commit c43b209 into ManageIQ:master Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants