Prevent heavy searches from causing latency issues

The Search Gateway allows you to:

  • Block heavy searches - automatically with customization options
  • Reject searches based on cluster health
  • Block or assign search rules per user
  • Disallow searches based on characteristics
  • Book Demo

The Search Gateway improves search performance

    Say goodbye to:
  • Experiencing slow searches
  • Searches causing down-time
  • Difficulties pinpointing heavy searches
  • Trouble preventing costly searches

Get deep visibility of searches

  • Visibility into - search “took” time, amount of searches over time, specific searches
  • Pinpointing heavy searches
  • Ability to group search stats by user
  • Real-time explanations for why searches became heavy and how to optimize heavy searches

FAQs

What is a heavy search?

A heavy search is a search that causes latency, not to be confused with a search that is slow due to existing latency in the system.

Can I configure what is defined as a “heavy search”?

Yes, you can. The Search Gateway is configured to protect the cluster out-of-the-box, but you have the ability to configure the settings according to your specific system.

What if I have a heavy search that I want to allow?

There are a number of options for allowing a specific search to run despite its size and resource utilization. You can configure the allowance according to user roles, specifications and other attributes.

Does the Search Gateway add load to your system and slow it down?

No, the Search Gateway works efficiently and async with the usual latency of less than a millisecond.

What if the cluster is loaded for reasons that have nothing to do with searches?

The Search Gateway knows how to identify when slow searches are causing load on your cluster, versus when searches are running slowly because your cluster is loaded for other reasons.

What are the hardware requirements?

The Search Gateway is a lightweight process that scans the requests efficiently and forwards them. Usually, 2 to 4 GB of memory with two cores will suffice, depending on the workloads.

Will the Search Gateway prevent heavy searches or just detect them?

You can use the Search Gateway in multiple ways. It can be used solely for detection, but its power lies in its ability to prevent heavy searches from breaking your cluster.

Does the Search Gateway replace the functionality of coordinating nodes?

No, you can think of the Search Gateway as a lightweight reverse proxy. The SG proxies the requests to the cluster, which then coordinates the search internally.

Can I identify searches and changes according to specific users?

Yes, with the visibility afforded by the Search Gateway you can group stats according to user and application.

What if the Search Gateway is down or unavailable?

As with any mission-critical network device, it’s recommended to have more than one for high availability purposes.

The Search Gateway comes out of the box with metrics and a Grafana dashboard to allow for easy set up of alerts. The Gateway is a lightweight process that can be restarted or removed quickly when needed.

Does it work out-of-the-box to protect my cluster?

Yes. The Search Gateway begins detecting your heavy searches right away upon installation. You can always adjust settings as needed.

Which Elasticsearch versions does the Search Gateway work with?

All versions!

Opster's Search Gateway Vs. Generic Monitoring Tools Vs. Slow Logs

Category
Monitoring Tools
The Search Gateway
Slow Logs
Basic search latency visibility
Amount of searches over time
Search “took” time
-
Drill down visibility for specific searches
-
Pinpointing heavy searches
-
-
Automatically Block heavy searches
-
-
Reject searches based on cluster health
-
-
Allow/disallow searches based on features
-
-
Block or assign search rules per user
-
-
Monitoring Tools
Basic search latency visibility
Amount of searches over time
Search “took” time
-
Drill down visibility for specific searches
-
Pinpointing heavy searches
-
Automatically Block heavy searches
-
Reject searches based on cluster health
-
Allow/disallow searches based on features
-
Block or assign search rules per user
-
Slow Logs
Basic search latency visibility
Amount of searches over time
Search “took” time
Drill down visibility for specific searches
Pinpointing heavy searches
-
Automatically Block heavy searches
-
Reject searches based on cluster health
-
Allow/disallow searches based on features
-
Block or assign search rules per user
-

Easily integrated into your own operation Stack

Whether you have an on-prem or cloud installation, Opster’s products can be integrated seamlessly into your own operation management stack. Contact us to see a demo of the Search Gateway.

See how the Search Gateway can improve your ES performance

Contact Us

Opster is not affiliated with Elasticsearch B.V Elasticsearch and Kibana are trademarks of Elasticsearch B.V