Skip to content
LogScale Self-Hosted Deployment
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

# Installing Load Balancers

When LogScale is deployed as a cluster, clients of the cluster should only need to use a single URL, rather than connecting to a single node within the cluster. This avoids overloading a single node because the load on individual nodes within the cluster is uneven. A load balancer:

- Distributes load across the individual nodes of the cluster, so that no single node is used for all client work

- Allows a single URL to be shared to communicate the cluster, even though the cluster may be made up of multiple nodes

- Enables individual nodes, and the number of individual nodes in the cluster, to change without clients needing to be aware of the differences

- Allows you to configure and accommodate for a LogScale cluster configuration with different explicit node types

> Language Server Protocol

> LogScale uses the Language Server Protocol to analyse correctness of the queries you type in the LogScale User Interface. The language server also provides features like documentation, syntax highlighting, and quick fixes.

> LogScale's User Interface communicates with the language server via websockets (WS). If you have a proxy, such as Apache2 or Nginx, in-front of your LogScale server, it may cause these feature not to work correctly. You should ensure that your websockets are correctly configured in your proxy.

For guidance for configuring different proxies for use within LogScale:

- Apache Reverse Proxy

- Caddy Reverse Proxy

- Nginx Reverse Proxy

- HAProxy Reverse Proxy

#### Enter search term