Advanced forecast configuration

Configure the default forecasting options.

The default forecasting options are configurable by adding a [forecasting] section to the opscenterd.conf file to propagate to all clusters, or adjusting the defaults per cluster in cluster_name.conf.


The location of the opscenterd.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/opscenterd.conf
  • Tarball installations: install_location/conf/opscenterd.conf


The location of the cluster_name.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf


  1. To propagate the configuration to all clusters, open opscenterd.conf for editing.
  2. Add a [forecasting] section with the following available configuration options:
    [forecasting] range_multiplier
    The multiplier for the query range needed to produce forecasts. The default multiplier is 3.
    [forecasting] required_data_percentage
    Minimum percent of past data required to forecast. The default value is 0.5.

    To generate a meaningful prediction, historical data is analyzed for a longer period than the range being forecasted. The default range multiplier is three times larger than the range being forecasted. For example, to forecast one month into the future, three months of data is analyzed.

    The following example decreases the default range multiplier for the forecast timeframe, and decreases the required percentage amount of historical data, which might be necessary for a newer cluster to forecast a trend. If there is not enough data when forecasting, an error indicates less than 50 percent of the required past data was available. After a cluster has more historical data to work with, increasing the forecasting configuration values can increase the accuracy of forecasted trends.
    range_multiplier = 3
    required_data_percentage = 0.25
  3. To adjust the defaults per cluster, open cluster_name.conf for editing and adjust the forecasting options as appropriate per cluster.
  4. Save the configuration file or files.
  5. Restart the OpsCenter daemon.