Viewing data gaps in chargeback execution results
Chargeback reports are generated based on data collected from supported data sources. Due to delays or issues in the flow of data from these data sources into BMC TrueSight Capacity Optimization, there can be data gaps for the Chargeback Engine.
By default, the maximum amount of time before all the data is imported into BMC TrueSight Capacity Optimization and made available to the Chargeback Engine, is 12 hours.
Data gaps can occur when data imported into BMC TrueSight Capacity Optimization is not made available to Chargeback for more than 12 hours.
The following examples are intended to provide a better understanding of this mechanism.
This topic contains the following sections:
Types of data gaps
Data gaps in BMC TrueSight Capacity Optimization are of the following types:
Types of data gaps
Some hours or samples are missing.
Datasource has lost some data.
Using the detailed gap information in Chargeback – Admin > Engine Status, verify that the corresponding data connector has no errors during that period. If there are no errors, then the original datasource simply did not have the data, and it may not be possible to recover it. Otherwise, it may be a case of a connector (ETL) error. See the next row.
Data for a set of series is missing for a full day or for multiple days.
The ETL or the datasource stopped working.
Look at the logs for the ETL (connector). If it is necessary to recover the data, reset the LASTCOUNTER and try running it again, as described in Working with ETLs.
Metrics for a set of series is missing.
Datasource does not contain this metric, or the ETL has never run.
The data gaps mentioned in the preceding table are notified in the Messages column of the Resource Data gaps table in the Chargeback > Cost models > Data Gaps.
Data gaps and Chargeback UoMs
For Chargeback details specific to BMC Cloud Lifecycle Management, there is a predefined list of UoMs that can be used to set prices for requestable offerings. Particular UoMs require the corresponding metric to be available in BMC TrueSight Capacity Optimization, as described in.
You must ensure that the BMC Cloud Lifecycle Management service catalog is making available only those UoMs for which the corresponding data is available, otherwise it is not possible to compute Chargeback data for service offering instances that use these UoMs.
Before you begin
Ensure that the required cost model is executed. for more details, see Executing a cost model.
To view data gaps
- Select Chargeback > Cost models.
The Cost models page is displayed.
- Click the name of the required cost model.
The details page of the selected cost model is displayed.
- Select the Results tab.
Execution details of the selected cost model are displayed in the Results tab. If any result is displayed in a yellow highlight, it indicates that the corresponding execution results have data gaps.
- For the required result with the data gap, click
The details page for Data gaps is displayed with the cost data gaps details such as target, composite and basic cost object, and unit of measurement. .
To view resource details for the selected data gap, click.
The Resource data gaps table is displayed in the Data gaps page. This table displays details for each resource that is included in the selected Cost Model.
If you click on the name of a resource under the Name column in the Resource Data Gaps table, BMC TrueSight Capacity Optimization takes you to Workspace > All systems and business drivers > System details.
By default, the Chargeback Store task runs each day and calculates costs of the last 5 days of the models. After the missing data is recovered, costs are automatically updated for the last 5 days at the next execution of the Chargeback Store task. You can increase the period of calculation by editing the run configuration of the Chargeback Store task.