@fangji, thanks for the confirmation. This did work for me after clearing the data files.

from ice.

@cdgraff it looks like you can use the breakdown feature of Ice. To use the breakdown feature and application group feature, first make sure you signed up the beta version of detailed billing file with resources and tag. Make sure you enabled the custom tags you mentioned. Verify you receive monthly billing file in the this format: -aws-billing-detailed-line-items-with-resources-and-tags--.csv.zip. Then you will need to subclass abstract class ResourceService and have your own bootstrap.groovy to create ProcessorConfig and ReaderConfig. See SampleMapDbResourceService.java and EddaResourceService.java for a sample of subclass.

In your subclass, you will need to override method "public String getResource(Account account, Region region, Product product, String resourceId, String[] lineItem, long millisStart)" to return a string (treated by Ice as resource group name) for each line item in the billing file. Then Ice can breakdown by resource groups.

from ice.

+1

Something that can enumerate tags from the billing data and auto-populate the "Group by" for Tags. That would be ideal. I am no programmer so unfortunately I have no clue how to accomplish this.

from ice.

@dwinter3 how many unique values does your custom tag have roughly?

from ice.

10 or 12.

David Winter | Director of Hosted Solutions
Zenoss, Inc. | Transforming IT Operations
[email protected] | 1.813.417.1830 or 1.512.333.4620 | Skype: davewinter3

On Aug 2, 2013, at 10:12 PM, fangji [email protected] wrote:

@dwinter3 how many unique values does your custom tag have roughly?

—
Reply to this email directly or view it on GitHub.

from ice.

+1 for @dwinter3 's suggestion.

More complex filtering should lead to code programming, obviously. But the simple filtering based on the distinct values of all custom tags would be perfect to most people who cannot write code. This requirement covers more than 90% of the relevant needs IMHO.

from ice.

@cdgraff @dwinter3 @pparth Please check out the item #6 in Advanced options on readme page. Make sure you pull the latest code

If your custom tags have limited number of value combinations (e.g. < 100), you can choose to set the following parameter in ice.properties, and Ice will generate resource group values for each line item in the billing file. Please be VERY careful about using this feature. Resource group values are generated by concatenating values of of all custom tags. If it results in a long list of resource group values, Ice performance will be greatly affected. Please make sure the custom tags exist in the header of the billing file.

specify your custom tags here. Multiple tags are delimited by ",". If specified, BasicResourceService will be used to generate resource groups for you.

PLEASE MAKE SURE you have limited number (e.g. < 100) of unique value combinations from your custom tags, otherwise Ice performance will be greatly affected.

ice.customTags=tag1,tag2

from ice.

Thanks you sir!

David Winter | Director of Hosted Solutions
Zenoss, Inc. | Transforming IT Operations
[email protected] | 1.813.417.1830 or 1.512.333.4620 | Skype: davewinter3

On Aug 14, 2013, at 10:23 PM, fangji [email protected] wrote:

@cdgraff @dwinter3 @pparth Please check out the item #6 in Advanced options on readme page. Make sure you pull the latest code

If your custom tags have limited number of value combinations (e.g. < 100), you can choose to set the following parameter in ice.properties, and Ice will generate resource group values for each line item in the billing file. Please be VERY careful about using this feature. Resource group values are generated by concatenating values of of all custom tags. If it results in a long list of resource group values, Ice performance will be greatly affected. Please make sure the custom tags exist in the header of the billing file.

specify your custom tags here. Multiple tags are delimited by ",". If specified, BasicResourceService will be used to generate resource groups for you.

PLEASE MAKE SURE you have limited number (e.g. < 100) of unique value combinations from your custom tags, otherwise Ice performance will be greatly affected.

ice.customTags=tag1,tag2

—
Reply to this email directly or view it on GitHub.

from ice.

Thanks! I m checking it!

from ice.

Thanks!!! great news! we are updating and testing... thanks again

from ice.

Our custom tags that we're interested on slicing the billing data yield around 150 unique combinations (around 20 discrete features, usually 1 per tenant, 8 tenants; both tenants and feature counts are growing). What options for optimisation are there, or are we better off coding our own ResourceService?

from ice.

@petemounce 150 unique combinations should be fine.

from ice.

We use this feature and work perfect! thanks!

from ice.

Does the configuration option expect the tags to be "user:TagName"?
I.E. ice.customTags=user:Project

This is the only way I have been able to get tags to show up in the application groups, but they seem to have no resources associated with them. All of the cost totals are 0.00

from ice.

@challahc You should the tag column name you see in your billing file. If your billing file has column "user:Project", then your setting is right.

from ice.

Hi @fangji , after 2 months using the tool, we now detect that "Details with Resource Groups" is not accurated really the difference is big, near to 50% of total billing. We are using latest release just in case, this happen with previous and latest versions.

Some info that I can provide to help with the debug?

Thanks!

from ice.

@cdgraff Please check out this topic on GG: https://groups.google.com/forum/#!topic/iceusers/zh6pBh0c7oA
and #54

You can choose to use original price for resource groups by setting ice.resourceGroupCost=original

Thanks
-Fang

from ice.