# Too many buckets

**URL:** <https://discuss.elastic.co/t/too-many-buckets/302275>\
**Category:** Elasticsearch\
**Created:** [April 12, 2022, 9:34pm UTC](https://discuss.elastic.co/t/too-many-buckets/302275 "2022-04-12T21:34:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mario-slowinski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario-slowinski/32/104313_2.png) [@mario-slowinski](https://discuss.elastic.co/u/mario-slowinski)\
**Post date:** [April 12, 2022, 9:34pm UTC](https://discuss.elastic.co/t/too-many-buckets/302275/1 "2022-04-12T21:34:20Z")

</div>

Hello

In environment with almost 200 hosts, each sends **metricbeat** (i.e. network metrics every 30 seconds) to single Elasticsearch cluster. There is a business requirement to visualize incoming network traffic bandwidth on specified network interface.  
Due to volume of hosts/data and that rates must calculated with `derivative` aggregation first, trying to show timeframe larger than few hours ends with _too many buckets error_.

It would be most convenient to store aggregation result in other index for further/other processing.  
I'm new to Elastic so maybe there is a better approach to achieve this.  
`GET _cluster/settings?include_defaults=true&filter_path=transient.search.max_buckets`

```json
{
  "transient" : {
    "search" : {
      "max_buckets" : "1000000"
    }
  }
}

```

---

<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:** [May 10, 2022, 9:34pm UTC](https://discuss.elastic.co/t/too-many-buckets/302275/2 "2022-05-10T21:34:35Z")

</div>

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