# Agregating Data with multiple retention policies

**URL:** <https://community.influxdata.com/t/agregating-data-with-multiple-retention-policies/3463>\
**Category:** Store\
**Tags:** influxdb, schema\
**Created:** [December 19, 2017, 9:32pm UTC](https://community.influxdata.com/t/agregating-data-with-multiple-retention-policies/3463 "2017-12-19T21:32:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darkmyr](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/darkmyr/32/695_2.png) [@Darkmyr](https://community.influxdata.com/u/Darkmyr)\
**Post date:** [December 19, 2017, 9:32pm UTC](https://community.influxdata.com/t/agregating-data-with-multiple-retention-policies/3463/1 "2017-12-19T21:32:39Z")

</div>

overall my company wants to have 3 stages at which data is stored.

For example we have a cpu metric that we have minute precision on.

we want minute precision for 3mo, then  
for data over 3mo old but younger than 1y we want hour precision, lastly  
for data over 1y, we want day precision until 5y.

At that point, data can be deleted.

Can you have multiple retention policies on one measurement, or will I need 3 different measurements?

ex: telegraf.3months.cpu  
telegraf.1year.cpu  
telegraf.5year.cpu  
or even  
telegraf.3months.cpu  
telegraf.1year.avg\_cpu  
telegraf.5year.avg\_cpu  
rather than  
telegraf.cpu  
telegraf.1yr\_cpu  
telegraf.5yr\_cpu