# Elastic agent an system Integrations generate infinite void indixes with infinite rollover **URL:** \ **Category:** Elasticsearch\ **Created:** [February 16, 2024, 3:36pm UTC](https://discuss.elastic.co/t/elastic-agent-an-system-integrations-generate-infinite-void-indixes-with-infinite-rollover/353478 "2024-02-16T15:36:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![hectorGC](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hectorgc/32/136368_2.png) [@hectorGC](https://discuss.elastic.co/u/hectorGC)\ **Post date:** [February 16, 2024, 3:36pm UTC](https://discuss.elastic.co/t/elastic-agent-an-system-integrations-generate-infinite-void-indixes-with-infinite-rollover/353478/1 "2024-02-16T15:36:00Z")
Suddenly after normal work of the team we suffered a big amount of metrics logs, looking at that we discovered that the integrations of elastic-agent and system indexes started to make rollover of all namespaces. Continuing doing rollover altougth they were with 0 documents until it reached the limit of shards. The ILM policies weren't change so far. There are some tasks that happenned before: A colleague incorporate a new agent, with system and elastic-agent integration Another modify some custom integration. Is quite weird to be honest. Any insigth or help? Let me know if you have questions as wells. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 15, 2024, 3:36pm UTC](https://discuss.elastic.co/t/elastic-agent-an-system-integrations-generate-infinite-void-indixes-with-infinite-rollover/353478/2 "2024-03-15T15:36:35Z")
Closed on March 15, 2024, 3:36pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.