Step 1: Verify Prerequisites for Linux Installation

System Requirements

Library Dependencies

  • libnss3 library

    • Debian/Ubuntu – sudo apt-get install libnss3
    • CentOS/RedHat – sudo yum install libnssutil3.
Skedler Alerts requires hostname of the server in which Skedler Alerts is installed to be configured in /etc/hosts. 

1.  Check hostname by giving this command: 


In alertConfig.yml the host parameter is the host in which Skedler Alerts binds.

2.  If the host is configured as then make sure you have an entry in /etc/hosts as mentioned below, localhost

     Note: If you are binding Skedler Alerts to localhost you can't access it from outside.      

3. However, if the bind address is in alertconfig.yml then Skedler Alerts binds to any IP (configured for your system). In this case, your entry in the hosts' file(/etc/hosts) should be

    <ipaddress> <hostname>

4.  If the host(IP address of the server) in alertConfig.yml is changed other than the default value then there should be an entry for the host in /etc. hosts like

     <ipaddress> <hostname>

 5.  Reboot the system.


Note: If you are using any proxy server add your hostname to a no_proxy list in the file /etc/environment add the following line,


Elasticsearch version

Skedler Alerts supports Elasticsearch version from 2.0 to 6.5.4

Step 2: Download

  • Download the latest version of Skedler Alerts from Download page.

Step 3: Extract

  • Extract the skedler-alerts.tar.gz file to the desired folder (e.g., /opt). For convenience, let us call this folder as $alert_home.

Step 4: Install Skedler Alerts

  • Provide the required permission to in $alert home script file using the command
  • cd $alert_home
  • sudo chmod u+x
  • Install Skedler Alerts using the below command. Run as sudo user
  • sudo ./

Step 5: Configure alertconfig.yml

  • Go to config folder using the command cd config.
  • Open alertconfig.yml (e.g., vi /opt/alert/config/alertconfig.yml)

      ElasticSearch  URL configuration

  • Add Elasticsearch URL with the port (even if the port is 80) in the alertconfig.yml file in the following format

      Proxy server basic authentication configuration

  • If you are using Nginx, follow the steps below.

    If Nginx is configured as a reverse proxy for Elasticsearch, configure Nginx username and password for Elasticsearch as shown:

  • Note: If you are using Shield then refer to Step-by-Step Configuration Guide for Shield.
  • Save changes to alertconfig.yml
For more configuration options please refer alertconfig.yml configuration.

Step 6: Start Skedler Alerts

You can start Skedler Alerts as a service or manually.
  • To start Skedler Alerts as a service, execute

               sudo service alert start  

  • To start Skedler Alerts manually

               Change directory to $alert_home (e.g., /opt/alert) and execute


Step 7: Access Skedler Alerts

Skedler Alerts can be activated Online or Offline. Refer the following articles to activate the license


Step 8: Schedule Skedler Alerts

To configure Skeldler Alerts settings, refer to How to configure time zone settings, index pattern settings, email settings, Webhook settings for skedler alerts

You are now ready to start scheduling Alerts.


Step 9: License Upgrade

Activation is required for purchased product license key. In the Community Edition, license activation will be skipped. If you purchase Skedler Alerts license, you will receive a license key by email.  


Refer to Upgrade License