# If I have syslogs from multiple types of devices and multiple ILM policies, how should I structure these? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 16, 2019, 8:59pm UTC](https://discuss.elastic.co/t/if-i-have-syslogs-from-multiple-types-of-devices-and-multiple-ilm-policies-how-should-i-structure-these/199727 "2019-09-16T20:59:58Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![wmassingham](https://avatars.discourse-cdn.com/v4/letter/w/e36b37/32.png) [@wmassingham](https://discuss.elastic.co/u/wmassingham)\ **Post date:** [September 16, 2019, 8:59pm UTC](https://discuss.elastic.co/t/if-i-have-syslogs-from-multiple-types-of-devices-and-multiple-ilm-policies-how-should-i-structure-these/199727/1 "2019-09-16T20:59:58Z")
I have syslogs from multiple types of network devices from multiple customers being processed by logstash. Our end goal is to sell different tiers of data retention. I'm thinking that if we can put a field in the syslog data, we can direct it to different indices in elasticsearch with logstash's elasticsearch output `index` option. But would it be more effective to use the `ilm_pattern` option and let ILM handle index creation? And, since there's no overlap between the devices, would it be more effective to split each type of device data into its own set of indices (e.g. logstash-firewall-_, logstash-switch-_)? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 14, 2019, 9:00pm UTC](https://discuss.elastic.co/t/if-i-have-syslogs-from-multiple-types-of-devices-and-multiple-ilm-policies-how-should-i-structure-these/199727/2 "2019-10-14T21:00:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.