Does Marvel's search rate include _suggest traffic?

monitoring

(David Kemp) #1

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


(Chris Earle) #2

Hi David,

In Elasticsearch 5.0, the _suggest endpoint rewrites itself as an embedded _search request with a suggest body. However, in Elasticsearch 2.x (2.3.1), 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:

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

versus

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:

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.


(system) #3