# "Design" considerations about indices from different beats? **URL:** \ **Category:** Beats\ **Created:** [April 19, 2017, 1:23pm UTC](https://discuss.elastic.co/t/design-considerations-about-indices-from-different-beats/82891 "2017-04-19T13:23:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Andreas\_Falk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreas_falk/32/82595_2.png) [@Andreas\_Falk](https://discuss.elastic.co/u/Andreas_Falk)\ **Post date:** [April 19, 2017, 1:23pm UTC](https://discuss.elastic.co/t/design-considerations-about-indices-from-different-beats/82891/1 "2017-04-19T13:23:21Z")
Hi, We do now have a working win/file - beats -\> kafka -\> logstash -\> ES dev setup. And with help from forum users everything is running as it should 🙂 A new thing that was introduced is the thought with different indices for different logtypes. In the dev env I written all output to logstash-date, but now thinking about splitting it up again. Are there any pro's to use different indices other than keeping it clean in the log output in kibana? All ideas and suggestions are welcome 🙂 -- Regards Falk ---
**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:** [April 20, 2017, 8:04am UTC](https://discuss.elastic.co/t/design-considerations-about-indices-from-different-beats/82891/2 "2017-04-20T08:04:52Z")
Separate means you can handle individual retention for each type. ---
**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, 2017, 1:35pm UTC](https://discuss.elastic.co/t/design-considerations-about-indices-from-different-beats/82891/3 "2017-05-10T13:35:02Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.