# Rolling up different status types **URL:** \ **Category:** Kibana\ **Tags:** rollups\ **Created:** [July 15, 2022, 6:31pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762 "2022-07-15T18:31:45Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Chicken\_Bake](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chicken_bake/32/99840_2.png) [@Chicken\_Bake](https://discuss.elastic.co/u/Chicken_Bake)\ **Post date:** [July 15, 2022, 6:31pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/1 "2022-07-15T18:31:45Z")
So i have a large amount of data being written to an index everyday. the main index is over written as the amount of data is quite large. The data consist of 3 fields per record and its a timestamp, status, extstatus. An example: timestamp: (random time stamp) status: complete extstatus: in progress How can i use the rollup function to save status on the data so i can track as things like the count of complete status or inprogress status from month to month? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 19, 2022, 2:50am UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/2 "2022-07-19T02:50:33Z")
Welcome to our community! 😃 > [@Chicken\_Bake](#): > > the main index is over written as the amount of data is quite large How large? ---
**Author:** ![Chicken\_Bake](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chicken_bake/32/99840_2.png) [@Chicken\_Bake](https://discuss.elastic.co/u/Chicken_Bake)\ **Post date:** [July 20, 2022, 3:45pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/4 "2022-07-20T15:45:04Z")
It is about 5,000 records with 70 fields. I guess not HUGE but its too much data in managements eyes to keep history of. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 20, 2022, 10:31pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/5 "2022-07-20T22:31:09Z")
It's all relative, but that's not a lot of data. A rollup like [Getting started with rollups | Elasticsearch Guide [8.3] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/rollup-getting-started.html) could work. ---
**Author:** ![Chicken\_Bake](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chicken_bake/32/99840_2.png) [@Chicken\_Bake](https://discuss.elastic.co/u/Chicken_Bake)\ **Post date:** [July 21, 2022, 4:46pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/6 "2022-07-21T16:46:30Z")
I have tried that and it does not roll up the data. Im thinking that maybe its because my timestamp field is named "last\_updated" instead of timestamp? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 21, 2022, 10:49pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/7 "2022-07-21T22:49:53Z")
It'd be useful if you shared the code of what you have tried. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 18, 2022, 10:50pm UTC](https://discuss.elastic.co/t/rolling-up-different-status-types/309762/8 "2022-08-18T22:50:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.