# Does Marvel's search rate include \_suggest traffic?

**URL:** <https://discuss.elastic.co/t/does-marvels-search-rate-include--suggest-traffic/54895>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [July 7, 2016, 4:11am UTC](https://discuss.elastic.co/t/does-marvels-search-rate-include--suggest-traffic/54895 "2016-07-07T04:11:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidbkemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidbkemp/32/594_2.png) [@davidbkemp](https://discuss.elastic.co/u/davidbkemp)\
**Post date:** [July 7, 2016, 4:11am UTC](https://discuss.elastic.co/t/does-marvels-search-rate-include--suggest-traffic/54895/1 "2016-07-07T04:11:00Z")

</div>

When using Marvel (version 2.3.1) to monitor search traffic, when I drill down to a particular index on the "Indices" tab, it is indicating that the index is not receiving any searches. This is despite me firing lots of "\_suggest" requests at the index.

So, I am wondering if the "search rate" does not include calls to the "\_suggest" end point?

Would it have included them if I embedded the suggest request inside of an ordinary "\_search" request?

Thanks,  
David

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [July 7, 2016, 5:19am UTC](https://discuss.elastic.co/t/does-marvels-search-rate-include--suggest-traffic/54895/2 "2016-07-07T05:19:32Z")

</div>

Hi David,

In Elasticsearch 5.0, the [`_suggest` endpoint](https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/rest/action/suggest/RestSuggestAction.java#L77) rewrites itself as an embedded `_search` request with a `suggest` body. However, in Elasticsearch 2.x ([2.3.1](https://github.com/elastic/elasticsearch/blob/v2.3.1/core/src/main/java/org/elasticsearch/rest/action/suggest/RestSuggestAction.java#L70)), it stays as a special `suggest` request.

Marvel is _only_ showing the `search` rate, which does not consider any `suggest` counts.

A quick test suggests (see what I did there?) that you're right. By running:

```http
GET /test/_suggest
{
  "text": "developig",
  "mine": {
    "term": {
      "field": "message"
    }
  }
}

```

versus

```http
GET /test/_search
{
  "size": 0,
  "suggest": {
    "text": "developig",
    "mine": {
      "term": {
        "field": "message"
      }
    }
  }
}

```

I was able to change the number of _search_ requests, which more appropriately reflects what is happening.

For reference, you can see this immediately / locally without Marvel here:

```http
GET /test/_stats

```

As a result, Monitoring in 5.0 should automatically do the right thing, while Marvel 2.3 will effectively miss this detail.

---

<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:** [July 6, 2017, 1:42pm UTC](https://discuss.elastic.co/t/does-marvels-search-rate-include--suggest-traffic/54895/3 "2017-07-06T13:42:46Z")

</div>