Custom time period setting must match with the aggregated data retention value

The setting in common Config Map for timeseries pre-aggregated data retention value must match with the custom time period setting.

Symptoms

Consider the following scenario. If you create a Busy hour definition with the following parameters:
  • Sliding mode = Non-sliding
  • Schedule name = EVERYMONTH
  • Time period= Last month
  • Granularity = Week or Month
You might notice that no Resource types are returned in the database when the Custom Time period selection from Run during the selected period (Run icon) is more than the default value for the timeseries.pre-agg.hourly.retention.period.inday setting. The default value for the timeseries.pre-agg.hourly.retention.period.inday setting is 32.

Resolving the problem

To resolve this issue, change the default value of the timeseries.pre-agg.hourly.retention.period.inday setting in common Config Map to a higher value. For example, timeseries.pre-agg.hourly.retention.period.inday=90
Note: Currently, it works only in fresh installation scenario.