Cost History OLAP Report API response contains many null value AWS-Accounts in a sub-organization

Products

• CloudHealth

Issue/Introduction

In a sub-organization the AWS-Account dimension returned by the REST API OLAP report call may contain "null" entries.  

Environment

CloudHealth
REST API
AWS
OLAP Report
Cost Report
FlexOrg
AWS-Account

Cause

This is expected behavior.  API users in a sub-organization will observe place holder "null" AWS Accounts for the accounts that are part of the top-level organization (TLOU) but are not assigned to the sub-organization (FlexOrg) they are a member of.  

Resolution

Users should be aware of this behavior.  No action is needed however any user code processing the API results of an OLAP report may wish to handle the null AWS-Account values and the data that they index.  These can be iterated over or pre-processed for removal in the customer application code as needed.  These cannot be removed from the api returned data set via parameter.  Another option is to create and use a Perspective based on AWS-Account as the dimension.    

Please also note for a given array of data values, that array length will be truncated after the location of the last actual value in it and if all of the remaining values in it would have been null.  This also should be considered in your processing of the data so as to not try to read data at an indexed location that does not exist.   

Also refer our Knowledge Base Article # 413404 about using the "collapse_null_arrays=1?" API parameter.  Use of this parameter can help reduce the returned data set size and improve performance.