In TrueSight Capacity Optimization, daily statistics for metrics are not consistently updated in SYS_DATA_ROLL table and the MAX in the SYS_DATA_ROLL is using MAX (AVGVALUE)

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization 11.3.01



    PROBLEM:

    It would almost appear that if the hourly samples are not warehoused by a certain time then the Last 1 day stat is never being refreshed. Perhaps it makes more sense for Last 1 day statistics to use the DETAIL tables instead of HOUR tables to avoid inconsistent refresh; or provide a global parameter to specify whether the TSCO DWH uses DETAIL samples by default instead of HOUR samples, since there is a loss of data accuracy for all statistics in the ROLL table when they are using HOUR samples if DETAIL is available instead.


    CAUSE:

    Defect DRCOZ-23385


    SOLUTION:

    The Last 1 day stat is never being refreshed. Perhaps it makes more sense for Last 1 day statistics to use the DETAIL tables instead of HOUR tables to avoid inconsistent refresh; or provide a global parameter to specify whether the TSCO DWH uses DETAIL samples by default instead of HOUR samples, since there is a loss of data accuracy for all statistics in the ROLL table when they are using HOUR samples if DETAIL is available instead.
    The Data warehouse considers to refresh 1 day roll only if the request evaluated by the reduce thread include any point of yesterday (with respect to current time).

    There’s another behavior implemented for a set of metrics (ROLLPERIOD=10024) to always consider last 24 hours from “last available point” instead of last 1 day. The current behavior of "Last 1D" hence is strictly connected with availability of yesterday samples aggregated at hour level and performances of the environment (queue age). Switching to DETAIL level will no more be valid for CO >=11.5 (both DETAIL and HOUR are computed by store thread so they’ll be available at same time). If we want to change the "1D behavior" it is possible but it might affect performances (similar to apply last 24 hours everywhere).

    Defect DRCOZ-23385 has been traced for this and will be released in:
        a. CHF 11.3.01.001.C00021
        b. CHF 11.5.01.000.C00005


    Article Number:

    000175019


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles