Service Operations Insight

Back to Library

Tech Tip: HOTFIX for ‘Regression Value Issue in BH_ROLLUP_HISTORY table’ (00369439/DE166263) 

Aug 16, 2016 10:11 AM

Problem: In CCC 2.9.2 and 2.9.3, the regression design allows to calculate regression values on rollup values from one day before (=yesterday) only. It is not possible to include data sources that are pulling in data that are older than one day.

 

Solution: The attached patch allows to calculate regression values for more than one day in the past, according to the value of the precalc.day.back key, which can be set in the defaults.properties file.

 

To deploy the patch on your system, follow these steps:

 

Before deploying the patch:

Unpack the attached RegressionValue_Patch.zip file. The zip file contains:

  • RollupMetricsWithBusinessHoursStep.class
  • BusinessHoursDao.class
  • IBusinessHoursMapper.class
  • IBusinessHoursMapper.xml

 

Deploy the class and xml files:

Windows:

  1. Make a backup copy of the following files:
  • <ccc_install_folder>\ApacheTomcat\webapps\ccc\WEB-INF\classes\com\hyperformix\hyfy\server\rollups\commands\triggeredUpdate\RollupMetricsWithBusinessHoursStep.class
  • <ccc_install_folder>\ApacheTomcat\webapps\ccc\WEB-INF\classes\com\hyperformix\pb\server\dao\BusinessHoursDao.class
  • <ccc_install_folder>\ApacheTomcat\webapps\ccc\WEB-INF\classes\com\hyperformix\pb\server\mapper\IBusinessHoursMapper.class
  • <ccc_install_folder>\ApacheTomcat\webapps\ccc\WEB-INF\classes\com\hyperformix\pb\server\mapper\IBusinessHoursMapper.xml

Linux:

  • <ccc_install_folder>/ApacheTomcat/webapps/ccc/WEB-INF/classes/com/hyperformix/hyfy/server/rollups/commands/triggeredUpdate/RollupMetricsWithBusinessHoursStep.class
  • <ccc_install_folder>/ApacheTomcat/webapps/ccc/WEB-INF/classes/com/hyperformix/pb/server/dao/BusinessHoursDao.class
  • <ccc_install_folder>/ApacheTomcat/webapps/ccc/WEB-INF/classes/com/hyperformix/pb/server/mapper/IBusinessHoursMapper.class
  • <ccc_install_folder>/ApacheTomcat/webapps/ccc/WEB-INF/classes/com/hyperformix/pb/server/mapper/IBusinessHoursMapper.xml

 

    2. Replace the class and xml files with the ones you extracted from the attached zip file.

 

Set up a custom number of metrics days for daily regression:

 

  1. Navigate to <ccc_install_folder>\ApacheTomcat\webapps\ccc\WEB-INF\classes (<ccc_install_folder>/ApacheTomcat/webapps/ccc/WEB-INF/classes) and open the defaults.properties file in a text editor.
  2. Append the following property at the end of the file, and set the value according to your preference:

# Number of past days to re-run rollup
precalc.day.back=2

    In this example, regression values will be calculated up to 2 days before today (=yesterday and the day before yesterday).

 

Restart the CCC service:

Windows:

  1. Click Start, Control Panel, Administrative Tools. Click Services.
  2. Select the Apache Tomcat 7.0 CA_CCC service and restart it.

Linux:

  1. In a terminal, navigate to the bin directory of Apache Tomcat Server: <ccc_install_folder>/ApacheTomcat/bin
  2. Do:

./stop.sh

./start.sh

Statistics
0 Favorited
1 Views
1 Files
0 Shares
0 Downloads
​
Attachment(s)
zip file
RegressionValue_Patch.zip   9 KB   1 version
Uploaded - May 29, 2019
 
Download

Tags and Keywords

Comments

Legacy User
Aug 17, 2016 09:23 AM

If you notice that your Regression table values have a lower confidence (column name: Data_Coverage_Perc) level, this may be what you need.

Data_Coverage_Perc - meaning - 100% indicates you have samples for all days in the period.  Less than 100% means you are missing some data during the interval period.

 

If you have loaded in data that is from more than 1 day in the past, you could have this problem...less than 100% in your Regression table values.

 

This fix allows you to set the number of days in the past to consider for rollup.

 

If you need to fix everything...  You can set the value to your largest Regression period.

Example: 6 months is largest regression interval

# Number of past days to re-run rollup
precalc.day.back=180

 

Just don't leave it set this way more than one day...then set it to the value of days in the past that you routinely load.

Example: Normally load data that is at most 2 days old.

# Number of past days to re-run rollup
precalc.day.back=2

 

For instance, if you load 3 data sources and they are prioritized to exclude anything that came in from a higher priority data source.

Your Load and Migrate schedule might load as shown below:

     Data Source 1 - VMWARE - the top priority would pull in 1 day old data.

     Data Source 2 - BMC - the 2nd priority would pull in 2 day old data.

     Data Source 3 - Other - the 3rd priority would pull in 3 day old data.

 

In this case if you use the Regression tables, you might see that you never get 100% confidence because BH_Rollups currently only considers data that is 1 day old.

 

This fix will allow you to set the

# Number of past days to re-run rollup
precalc.day.back=3

 

 

Then you will have data points for all regression intervals, which gives you a score of 100% Data_Coverage_Perc.

Related Entries and Links

No Related Resource entered.