# Get queries / sec metric

**URL:** <https://discuss.elastic.co/t/get-queries-sec-metric/72236>\
**Category:** Elasticsearch\
**Created:** [January 19, 2017, 11:43pm UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236 "2017-01-19T23:43:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\
**Post date:** [January 19, 2017, 11:43pm UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/1 "2017-01-19T23:43:07Z")

</div>

We want to monitor live traffic (incoming and outgoing) to cluster. I can't seem to find a way to fetch queries / sec. What is the metric I should be looking at?

Some metrics I looked at but they don't seem to get what we want:  
indices.search\_fetch\_current : doesn't work because it includes counts for each shard  
http.current\_open: these are HTTP connections, we use 9300 port for connections  
transport.server\_open: these seem to include all kinds of connections, so can't differentiate search and index queries

We have installed telegraf plugin: [https://github.com/influxdata/telegraf/tree/master/plugins/inputs/elasticsearch](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/elasticsearch)

Please let me know. Thank you.

---

<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:** [January 21, 2017, 8:34am UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/2 "2017-01-21T08:34:51Z")

</div>

There is no metric for this.  
Monitoring (the plugin) calculates this itself.

---

<div class="post-metadata">

**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\
**Post date:** [January 21, 2017, 5:01pm UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/3 "2017-01-21T17:01:00Z")

</div>

Did you mean Kibana?

---

<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:** [January 21, 2017, 10:31pm UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/4 "2017-01-21T22:31:48Z")

</div>

[https://www.elastic.co/guide/en/x-pack/current/xpack-monitoring.html](https://www.elastic.co/guide/en/x-pack/current/xpack-monitoring.html)

---

<div class="post-metadata">

**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\
**Post date:** [January 23, 2017, 11:13pm UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/5 "2017-01-23T23:13:37Z")

</div>

Thanks Mark. As far as I understand, x-pack also does show the expose incoming queries. What it seems to display on graph are the queries to each shard, which might not necessarily be the same.

This is based on the tech talk on the website of X-Pack. However, it is for version 2.3, not sure if things have changed in version 5 (we are using 5.1.1). Please let me know.

---

<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:** [January 24, 2017, 2:38am UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/6 "2017-01-24T02:38:40Z")

</div>

You can see cluster, node and shard level stats with Monitoring.

---

<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:** [February 21, 2017, 2:39am UTC](https://discuss.elastic.co/t/get-queries-sec-metric/72236/7 "2017-02-21T02:39:18Z")

</div>

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