# System design for monitoring more than 1250 nodes

**URL:** <https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820>\
**Category:** Elasticsearch\
**Created:** [July 2, 2015, 5:05pm UTC](https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820 "2015-07-02T17:05:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChiBiPonD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chibipond/32/15859_2.png) [@ChiBiPonD](https://discuss.elastic.co/u/ChiBiPonD)\
**Post date:** [July 2, 2015, 5:05pm UTC](https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820/1 "2015-07-02T17:05:24Z")

</div>

Does anyone can help me design the suitable system for monitoring 1250 nodes at 600kHz? I have no idea how many elasticsearch master nodes I need. Or should I really have to use Logstash for input instead of doing direct curl to the master node. Thank you in advance.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 2, 2015, 8:23pm UTC](https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820/2 "2015-07-02T20:23:49Z")

</div>

You keep asking the same question and you've received a couple of answers, including advice to drop the idea of using curl commands to insert data.

If you're going to get anywhere _near_ 600k insertions/s you're going to need a bunch of nodes for the indexing alone, but if you're going to store data for any time at all you're going to need a huge cluster anyway. 600k/s is almost 52 billion documents per day. To give you some kind of idea, I have a three-node cluster for two billion documents.

The [Performance Considerations for Elasticsearch Indexing](https://www.elastic.co/blog/performance-considerations-elasticsearch-indexing) blog post from September 2014 contains a number of considerations. More recently there was also a blog post about how to estimate the size of clusters. I suggest you start there.

---

<div class="post-metadata">

**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:** [July 2, 2015, 9:58pm UTC](https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820/3 "2015-07-02T21:58:12Z")

</div>

> [@magnusbaeck](#):
>
> You keep asking the same question and you've received a couple of answers

Yep, please use one of your existing threads @ChiBiPonD 🙂

---

<div class="post-metadata">

**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:** [July 2, 2015, 9:58pm UTC](https://discuss.elastic.co/t/system-design-for-monitoring-more-than-1250-nodes/24820/4 "2015-07-02T21:58:16Z")

</div>


