We are on a long-term path to greater cloud usage and I am trying to figure out how much massaging of cloud data I should do. Right now, we have some grouping to reduce the total number of rows to a more manageable level within Apptio but I worry about losing some of the usefulness of the granular detail.

So - do you group your cloud data within Apptio? If so, what do you find to be an acceptable level? If not, do you have problems with the sheer number of rows, especially with AWS data?

Robert Krauss I group our cloud data by app tag value since that's really the most meaningful value to our group getting cloud cost information from CT. We also have Cloudability though, so that's where our folks go to see their cloud data from every conceivable lens. Operational costs and usage insights at the service, product, application, requestor, department, etc. are gleaned from Cloudability so in Cost Transparency I can aggregate at the application level for allocation and cost data consumption. I think it really depends on what your users are trying to see in their reporting, and then what level of trade off between granularity and calc times they're willing to bear.