# Inaccuracy and noises in elastic search rollup data

**URL:** <https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014>\
**Category:** Elasticsearch\
**Tags:** rollups\
**Created:** [March 19, 2023, 9:33am UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014 "2023-03-19T09:33:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehrab\_Azad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehrab_azad/32/118026_2.png) [@Mehrab\_Azad](https://discuss.elastic.co/u/Mehrab_Azad)\
**Post date:** [March 19, 2023, 9:33am UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014/1 "2023-03-19T09:33:26Z")

</div>

I am new to the ELK stack and Elasticsearch. I am currently storing nginx logs in Elasticsearch and using Kibana to visualize the total bytes over time. The purpose of this is to monitor traffic. To reduce storage requirements, I am trying to roll up the data into 1-minute intervals. However, the resulting visualization has a lot of noise. If I increase the time interval to 20 or 30 minutes, the visualization improves significantly. However, I need to store the data in 1-minute intervals. Is this a common issue? Can it be resolved? My Elasticsearch stack version is 8.2.2.

I have rolled up data via kibana itself, and the request for that is like this:

```auto
PUT _rollup/job/test
{
  "id": "test",
  "index_pattern": "nginx-optimized-2023.03.04",
  "rollup_index": "test",
  "cron": "0 * * * * ?",
  "page_size": 1000,
  "groups": {
    "date_histogram": {
      "interval": "1m",
      "field": "@timestamp"
    }
  },
  "metrics": [
    {
      "field": "bytes",
      "metrics": [
        "sum"
      ]
    }
  ]
}

```

---

<div class="post-metadata">

**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:** [March 19, 2023, 8:18pm UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014/2 "2023-03-19T20:18:02Z")

</div>

Welcome to our community! 😃

> [@Mehrab\_Azad](#):
>
> However, the resulting visualization has a lot of noise. If I increase the time interval to 20 or 30 minutes, the visualization improves significantly

It'd be good if you could share what you mean by this, screenshots etc.

---

<div class="post-metadata">

**Author:** ![Mehrab\_Azad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehrab_azad/32/118026_2.png) [@Mehrab\_Azad](https://discuss.elastic.co/u/Mehrab_Azad)\
**Post date:** [March 19, 2023, 10:02pm UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014/3 "2023-03-19T22:02:09Z")

</div>

thanks alot.

I have an index for 1 day data of nginx logs that has the outgoing bytes on each request.  
the index has 230127924 documents.  
And the rollup has 1440 documents, with 1 minute intervals.

 ![Screenshot from 2023-03-20 01-30-41](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3e8c3c1805f9f063f056df6097da006226d4260a.png)

the top visualization belongs to the data before rolling up, and the bottom after rolling up.

---

<div class="post-metadata">

**Author:** ![Mehrab\_Azad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehrab_azad/32/118026_2.png) [@Mehrab\_Azad](https://discuss.elastic.co/u/Mehrab_Azad)\
**Post date:** [March 28, 2023, 7:13am UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014/4 "2023-03-28T07:13:38Z")

</div>

Anything would be really helpful...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 25, 2023, 7:14am UTC](https://discuss.elastic.co/t/inaccuracy-and-noises-in-elastic-search-rollup-data/328014/5 "2023-04-25T07:14:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.