# Configure metrics rollup

Learn how to configure metrics rollup on your Kloudfuse cluster.

## Disabling metrics rollup

Starting with version 3.5.3, metrics rollup is enabled by default. To disable it, set `rollupEnabled` to `false` in your `custom_values.yaml` file:

Disable metrics rollup

```yaml
global:
  metrics:
    rollupEnabled: false
```

## Configuring rollup resolutions

Starting with version 3.5.3, Kloudfuse rolls up metrics at multiple resolution granularities. The resolutions are derived from a base interval (`rollupIntervalSecs`) and a set of multiplier factors (`rollupResolutionFactors`).

By default, the base interval is **300 seconds (5 minutes)** and the factors are **1, 2, 6, 12, 48**, which produces the following resolutions:

| Factor | Calculation | Resolution |
| --- | --- | --- |
| 1 | 300 x 1 | 5 minutes |
| 2 | 300 x 2 | 10 minutes |
| 6 | 300 x 6 | 30 minutes |
| 12 | 300 x 12 | 1 hour |
| 48 | 300 x 48 | 4 hours |

To customize the resolutions, set `rollupIntervalSecs` and `rollupResolutionFactors` in your `custom_values.yaml` file:

Configure rollup resolutions

```yaml
global:
  metrics:
    rollupIntervalSecs: 300
    rollupResolutionFactors:
      - 1
      - 2
      - 6
      - 12
      - 48
```

The query service automatically selects the most appropriate resolution based on the query’s step size and time range. For shorter time ranges or smaller step sizes, raw metrics are used. For longer time ranges, a coarser rollup resolution is selected to improve query performance.

## Retention

By default, rolled up metrics have the same retention policy as raw metrics. To use a longer retention period for rollups, add the retention policy to the `global.retentionPolicy` section of your `custom_values.yaml` file:

Set the retention policies for metrics

```yaml
metrics:
  default:
    retentionTimeValue: 30
    retentionTimeUnit: DAYS
    retentionTimeRollupValue: 60
    retentionTimeRollupUnit: DAYS
```

## Mixed data

When some older data has no corresponding rolled up data, the query service automatically handles this by splitting the query. It uses the raw `kf_metrics` table for the older portion and the rolled up `kf_metrics_rollup` table for the newer portion, then merges the results before returning them.