This guide describes the recommended way to install Graylog on SUSE Linux Enterprise Server 13 and 15. All links and packages are present at the time of writing.

Warning: This guide does not cover security settings! The server administrator must make sure the Graylog server is not publicly exposed and is following security best practices.


Hint: This guide assumes that any firewall is disabled and traffic can flow across all necessary ports.

Graylog 5.0 requires the following to maintain compatibility with its software dependencies: 

  • OpenJDK 17 (This is embedded in Graylog 5.0 and does not need to be separately installed.)
  • OpenSearch 1.x, 2.x (or Elasticsearch 7.10.2)
  • MongoDB 5.x or 6.x

Additionally, the following patterns are required for a minimal setup (see SUSE 15 SP3 Deployment Guide):

- Base System
- Minimal System (Appliances)
- YaST configuration packages


Installing MongoDB on SUSE should follow the tutorial for SUSE from the MongoDB documentation. Graylog 5.0 is compatible with MongoDB 5.x-6.x.

1. Import the MongoDB public key.

sudo rpm --import

2. Add the MongoDB repository.

sudo zypper addrepo --gpgcheck "" mongodb

3. Install the MongoDB packages.

sudo zypper -n install mongodb-org

4. Then, start the MongoDB instance.

sudo systemctl daemon-reload
sudo systemctl start mongod.service

5. In order to automatically start MongoDB on system boot, you have to activate the MongoDB service by running the following command:

sudo systemctl enable mongod.service

Hint: For the following sections on OpenSearch and Elasticsearch, select which data node you will be using for your Graylog instance and complete only the requisite section.


If you are using OpenSearch as your data node, then follow the steps below to install OpenSearch 2.5.0.

Hint: These installation steps assume you are using Zypper as your package manager with SUSE.

1. You may prefer to disable transparent hugepages to improve performance before installing:

sudo su

cat > /etc/systemd/system/disable-transparent-huge-pages.service <<EOF
Description=Disable Transparent Huge Pages (THP)
ExecStart=/bin/sh -c 'echo never | tee /sys/kernel/mm/transparent_hugepage/enabled > /dev/null'

sudo systemctl daemon-reload
sudo systemctl enable disable-transparent-huge-pages.service
sudo systemctl start disable-transparent-huge-pages.service

2. Install the OpenSearch GPG key:

sudo rpm --import

3. Download the OpenSearch 2.5.0 package:


4. From the CLI, you can install the package.

sudo curl -SL -o /etc/zypp/repos.d/opensearch-2.x.repo
sudo zypper update
sudo zypper install opensearch

5. For rpm x64.

sudo rpm -ivh opensearch-2.5.0-linux-x64.rpm

6. Edit the opensearch.yml file:

sudo nano /etc/opensearch/opensearch.yml

7. At a minimum the following changes are required (for a single instance install):

Copy /var/lib/opensearch
path.logs: /var/log/opensearch
action.auto_create_index: false true  
discovery.type: single-node
indices.query.bool.max_clause_count: 32768

8. After the installation succeeds, enable the OpenSearch service:

sudo systemctl daemon-reload
sudo systemctl enable opensearch.service
sudo systemctl start opensearch.service

9. Then, enable and start OpenSearch:

sudo systemctl start opensearch

10. Finally, verify that OpenSearch launched correctly:

sudo systemctl status opensearch


Elasticsearch 7.10.2 is the only version that is compatible with Graylog 5.0; however, we recommend OpenSearch for new Graylog cluster installations.

The following commands will begin the installation of the open-source version of Elasticsearch. See the Elasticsearch install page for more detailed instructions.

1. First install the Elasticsearch GPG key with:

rpm --import

2. Then add the repository file /etc/zypp/repos.d/elasticsearch.repo with the following contents:

echo "[elasticsearch-7.10.2]
name=Elasticsearch repository for 7.10.2 packages
type=rpm-md" | sudo tee /etc/zypp/repos.d/elasticsearch.repo

3. Install the 7.10.2 release with:

sudo zypper install elasticsearch-oss

Graylog Configuration for Elasticsearch

1. Make sure to modify the Elasticsearch configuration file (/etc/elasticsearch/elasticsearch.yml), set the cluster name to Graylog, and uncomment action.auto_create_index: false to enable the action:

sudo tee -a /etc/elasticsearch/elasticsearch.yml > /dev/null <<EOT graylog
action.auto_create_index: false

2. In order to automatically start Elasticsearch on system boot, you must activate the Elasticsearch service by running the following commands:

sudo systemctl daemon-reload
sudo systemctl enable elasticsearch.service
sudo systemctl start elasticsearch.service


1. First install the Graylog GPG key with:

rpm --import

2. Then add the repository file /etc/zypp/repos.d/graylog.repo with the following content:


3. After that, install the latest Graylog Open release with:

sudo zypper install graylog-server

If you are installing Graylog Operations, then you will use the following command:

sudo zypper install graylog-enterprise

Edit the Configuration File

Read the instructions within the configurations file and edit as needed, located at /etc/graylog/server/server.conf. Additionally add password_secret and root_password_sha2 as these are mandatory and Graylog will not start without them.

1. You can use the following command to create your password_secret:

cat /dev/urandom | base64 | cut -c1-96 | head -1

2. You will then need to use the following command to create your root_password_sha2:

echo -n "Enter Password: " && head -1 </dev/stdin | tr -d '\n' | sha256sum | cut -d" " -f1

3. To be able to connect to Graylog, set http_bind_address to the public host name or a public IP address of the machine with which you can connect. More information about these settings can be found in Configuring the web interface.

Hint: If you’re operating a single-node setup and would like to use HTTPS for the Graylog web interface and the Graylog REST API, it’s possible to use NGINX or Apache as a reverse proxy.

4. The last step is to enable Graylog during the operating system’s startup:

sudo systemctl daemon-reload
sudo systemctl enable graylog-server.service
sudo systemctl start graylog-server.service

Now you can ingest messages into your new Graylog Cluster and extract the messages with extractors or use pipelines to work with the messages.

Cluster Setup

If you plan to have multiple servers assuming different roles in your cluster like we have in this big production setup you need to modify only a few settings. This is covered in our multi-node setup guide. The default file location guide lists the locations of the files you need to modify.