# Asking for Filebeat and Logstash configuration design advice **URL:** \ **Category:** Elasticsearch\ **Created:** [November 30, 2017, 9:49am UTC](https://discuss.elastic.co/t/asking-for-filebeat-and-logstash-configuration-design-advice/109722 "2017-11-30T09:49:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![przemolb](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@przemolb](https://discuss.elastic.co/u/przemolb)\ **Post date:** [November 30, 2017, 9:49am UTC](https://discuss.elastic.co/t/asking-for-filebeat-and-logstash-configuration-design-advice/109722/1 "2017-11-30T09:49:19Z")
Hello, I am new to Elastic stack so please be gentle 🙂 I'd like to ask you for an advice for Filebeat and Logstash configuration in the following world: There are X servers: S1, S2, S3, ... Sx Servers have the following logs to be shipped to Elastic stack: - system logs (/var/log/\*) and combination of application logs: - app1 logs (/opt/app1/logs/\*) - app2 logs (/opt/app2/logs/\*) - ... - appX logs (/opt/appX/logs/\*) My question is how to organize filebeat and logstash configuration to be able in Kibana/Elasticsearch: - quickly find logs from appX from Sx server - quickly find logs from appX across Sx - Sy servers - quickly find logs from system logs from Sx server - quickly find logs from system logs from Sx - Sy server How about indices ? Should I put system logs from each server into different index (X indices) or one index combined for all servers ? The same for applications: one index for all appX across all servers or one index for appX for each server ? ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [December 1, 2017, 8:14am UTC](https://discuss.elastic.co/t/asking-for-filebeat-and-logstash-configuration-design-advice/109722/2 "2017-12-01T08:14:02Z")
you might want to ask this in the respective beats and logstash forum, as the chance us much higher to get help, compared to Elasticsearch forum. I also refrained from moving this post, as it kind of belongs in both groups. So please go ahead yourself. Thanks! ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [December 1, 2017, 8:24am UTC](https://discuss.elastic.co/t/asking-for-filebeat-and-logstash-configuration-design-advice/109722/3 "2017-12-01T08:24:34Z")
You can [add a field to each prospector indicating the application](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html#configuration-fields) already when you collect data in Filebeat. If you combine this with [a field that contains a server identifier at the instance level](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-general-options.html#libbeat-configuration-fields) you can use these two parameters in Kibana to filter by server and/or application, Sio there is no need to have separate indices. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 29, 2017, 8:24am UTC](https://discuss.elastic.co/t/asking-for-filebeat-and-logstash-configuration-design-advice/109722/4 "2017-12-29T08:24:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.