# Beats - custom index issue **URL:** \ **Category:** Beats\ **Created:** [April 11, 2019, 5:28pm UTC](https://discuss.elastic.co/t/beats-custom-index-issue/176467 "2019-04-11T17:28:29Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![S\_Chase](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s_chase/32/33237_2.png) [@S\_Chase](https://discuss.elastic.co/u/S_Chase)\ **Post date:** [April 11, 2019, 5:28pm UTC](https://discuss.elastic.co/t/beats-custom-index-issue/176467/1 "2019-04-11T17:28:29Z")
With Heartbeat, Filebeat, and Metricbeat I tried to set a custom index - same name just removing the date. So instead of heartbeat-%{[agent.version]}-%{+yyyy.MM.dd} I was trying to make it: heartbeat-%{[agent.version]}" My plan then was to use 6.7's index lifecycle policy to let it roll over when it hits 50G. Main reasoning for that is to save shards. Those 3 alone per month would be 90 shards versus probably - 3 or less. I set each of them with this (using heartbeat as example). ``` heartbeat.elasticsearch.index: "heartbeat-%{[agent.version]}" setup.template.name: "heartbeat" setup.template.pattern: "heartbeat*" ``` as well as: `setup.dashboards.index: "heartbeat*"` But then index's won't show in kibana, and if I look at the logs I'll see something like: ``` Connection to backoff(elasticsearch(http://localhost:9200)) established Failed to publish events: temporary bulk send failure ``` If I go back and remove the custom name part - it will send without issue again. Any ideas? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 9, 2019, 7:28pm UTC](https://discuss.elastic.co/t/beats-custom-index-issue/176467/2 "2019-05-09T19:28:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.