# Performance Monitoring query **URL:** \ **Category:** Elasticsearch\ **Created:** [October 13, 2017, 8:58am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858 "2017-10-13T08:58:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![moriol](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@moriol](https://discuss.elastic.co/u/moriol)\ **Post date:** [October 13, 2017, 8:58am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858/1 "2017-10-13T08:58:18Z")
I am running a 3 node cluster and basically I want to see how many writes per second I have to my index in ES. I know X-pack is good for this to give me monitoring functionality, but before I install it on my 3 node cluster, I want to just monitor these rates command line. Is it possible command line, just to list how many writes I have to a particular index per second? I see there are many command for displaying cluster state,what can I issue just to to see Index Rate per second? The command below almost gives me too much, all I want is a representation command line of what Monitoring in Kibana would give me, for Index rate p/s curl -XGET 'localhost:9200/xyz/\_stats?pretty' ---
**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:** [October 13, 2017, 9:39am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858/2 "2017-10-13T09:39:32Z")
You need something which collects that information and aggregate over time. This is basically what XPack does behind the scene. Note that monitoring in x-pack is available for free with the basic license. Anyway, have a look at: - [https://www.elastic.co/guide/en/elasticsearch/reference/5.6/indices-stats.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/indices-stats.html) - [https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cluster-nodes-stats.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cluster-nodes-stats.html) ---
**Author:** ![moriol](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@moriol](https://discuss.elastic.co/u/moriol)\ **Post date:** [October 13, 2017, 9:42am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858/3 "2017-10-13T09:42:30Z")
X-pack sounds great but I believe I read its best to install on separate server to my ES cluster? I dont have a spare VM at the moment. I don't want to reload my current cluster at the moment as well, and I believe this is manditory when installing X-pack? I found the following command that does what I need, maybe useful for others too: curl -XGET 'localhost:9200/\_cat/count/twitter?v&pretty' I can initiate this count command and see per second, what has been written to my index, easy to calculate per second the write. ---
**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:** [October 13, 2017, 11:03am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858/4 "2017-10-13T11:03:31Z")
> [@moriol](#): > > X-pack sounds great but I believe I read its best to install on separate server to my ES cluster? I dont have a spare VM at the moment. It depends but yes having a separate monitoring cluster is a nice thing to do. Our gold and platinum customers can have for free a monitoring cluster that we manage on [cloud.elastic.co](http://cloud.elastic.co). > [@moriol](#): > > I don't want to reload my current cluster at the moment as well, and I believe this is manditory when installing X-pack? Yes. You have to restart your nodes. I think that rolling upgrade might work though. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 10, 2017, 11:03am UTC](https://discuss.elastic.co/t/performance-monitoring-query/103858/5 "2017-11-10T11:03:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.