# Trimming data from prometheus

**URL:** <https://community.cratedb.com/t/trimming-data-from-prometheus/992>\
**Category:** CrateDB\
**Created:** [January 19, 2022, 11:47am UTC](https://community.cratedb.com/t/trimming-data-from-prometheus/992 "2022-01-19T11:47:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jayeff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/jayeff/32/271_2.png) [@jayeff](https://community.cratedb.com/u/jayeff)\
**Post date:** [January 24, 2022, 8:30am UTC](https://community.cratedb.com/t/trimming-data-from-prometheus/992/5 "2022-01-24T08:30:49Z")

</div>

> I think the idea behind selecting the first 10 minutes of every hour was to ensure a sufficient amount of the prometheus scraped data was retained to make it useful. I may of course be able to reduce this.

If this is intended everything is well. I thought maybe this is unintentional and the script is expected to keep data for the whole hour 😀

Potentially our guide on [Sharding and Partitioning for Time Series Data](https://community.cratedb.com/t/sharding-and-partitioning-guide-for-time-series-data/737) could be interesting for you as well to find an efficient sharding strategy to optimise your query performance.

---

_[View the full topic](https://community.cratedb.com/t/trimming-data-from-prometheus/992)._