The Search Gateway improves search performance

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.

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.

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.

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

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.

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.

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.

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.

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

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.

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

All versions!