# Solution Design **URL:** \ **Category:** Elasticsearch\ **Created:** [February 10, 2020, 5:22am UTC](https://discuss.elastic.co/t/solution-design/218510 "2020-02-10T05:22:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Shalinicts](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shalinicts/32/81251_2.png) [@Shalinicts](https://discuss.elastic.co/u/Shalinicts)\ **Post date:** [February 10, 2020, 5:22am UTC](https://discuss.elastic.co/t/solution-design/218510/1 "2020-02-10T05:22:21Z")
What would be the good solution to monitor application and infra logs of servers implemented in GCP . Considering server count ~500 servers (Most of them RHEL 6.x) Logs:Infra Logs , 2 Application Logs per server Will the below solution is ideal? Beats -\> Kafka -\>Logstash-\>Elasticsearch-\>Kibana where in Beats will collect the logs from all the agents. 2 Kafka servers , 2 Logstash servers for load balancing , 6 Node ES with 3 master and 3 data nodes, 1 Windows server for Kibana. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 9, 2020, 5:22am UTC](https://discuss.elastic.co/t/solution-design/218510/2 "2020-03-09T05:22:31Z")
Closed on March 9, 2020, 5:22am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.