# How should I configure ELK stack for saving logs everyday?

**URL:** https://discuss.elastic.co/t/how-should-i-configure-elk-stack-for-saving-logs-everyday/141399
**Category:** Elasticsearch
**Created:** [July 24, 2018, 2:09pm UTC](https://discuss.elastic.co/t/how-should-i-configure-elk-stack-for-saving-logs-everyday/141399 "2018-07-24T14:09:47Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![abhishek0010](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@abhishek0010](https://discuss.elastic.co/u/abhishek0010)
#### Post date: [July 24, 2018, 2:09pm UTC](https://discuss.elastic.co/t/how-should-i-configure-elk-stack-for-saving-logs-everyday/141399/1 "2018-07-24T14:09:48Z")

</div>

I have a requirement which needs to have log indices for a period of 30 days, but the problem here is each index could grow to a potential size of more than 9 GB i.e. more than 10 million record per day.

Previously we deployed this setup within a single node cluster and after a significant amount of execution, the kibana dashboard was not able to query the specified index and was throwing timeout errors.

Since I am a noob, I dont have enough expertise about what kind of configuration we can use to resolve this issue.

Whether I should a single node cluster with more size ( I know it is prone to single point failure, but its an option), or opt for a multinode cluster? How to decide the multinode number? What should be the setting for the individual log index, i.e. whether it should have 5 shards or more? Is there any standard architecture for doing this?

Can someone help?

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 24, 2018, 2:29pm UTC](https://discuss.elastic.co/t/how-should-i-configure-elk-stack-for-saving-logs-everyday/141399/2 "2018-07-24T14:29:35Z")

</div>

May I suggest you look at the following resources about sizing:

[https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)

> **[How many shards should I have in my Elasticsearch cluster?
	  	 | Elastic](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**
>
> Elasticsearch is a very versatile platform, that supports a variety of use cases, and provides great flexibility around data organisation and replication strategies. This flexibility can however somet...

> **[NetSecureDay: Managing your Black Friday Logs](https://speakerdeck.com/elastic/netsecureday-managing-your-black-friday-logs)**
>
> Surveiller une application complexe n’est pas une tâche aisée, mais avec les bons outils, ce n’est pas si sorcier. Néanmoins, des périodes fortes telles que les opérations de type « Black Friday » (Vendredi noir) ou période de Noël peuvent pousser...

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 21, 2018, 2:29pm UTC](https://discuss.elastic.co/t/how-should-i-configure-elk-stack-for-saving-logs-everyday/141399/3 "2018-08-21T14:29:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
