Elasticsearch and Kibana version

Step 2: Download

Step 3: Extract

Step 4: Configure Permission

• Change the current directory (or go) to the folder where skedler.zip was extracted. For convenience, let us call this folder as $skedler_home.
  
• Provide read/write permissions to the following folders.
  
  • $skedler_home\log
  • $skedler_home\reports

Step 5: Configure reporting.yml

• Go to the config folder using the command cd config.
• Open reporting.yml (e.g., vi /opt/skedler/config/reporting.yml) 
  • Skedler security configuration
    • To use the security plugin and therefore, the authenticated users of ELK or Grafana for user-based report creation and generation, follow the below configuration  

    • # To use security users of ELK or Grafana for user-based report creation and generation, uncomment the variable and set the value to `false`. By default the variable value is set to `true`
      
      skedler_anonymous_access: false

      
      

  • Datastore configuration

    • Skedler needs a datastore to store Skedler metadata and history data. By default, Skedler uses Internal Database as a Datastore. Alternatively, you can configure either Elasticsearch or an external  "MySQL" or "SQLite"  database as a Datastore.

      • If you would like to use Elasticsearch as a Datastore (especially if you are upgrading from v3.x), follow the configuration shown below:
        1. Add Elasticsearch URL with the port (even if the port is 80) in the reporting.yml file in the following format <protocol>://<server>:<port>

        # The Elasticsearch instance to use for all your queries.
        elasticsearch_url: "http://localhost:9200"

        
        

        2. If any security plugin is configured for Elasticsearch such as X-pack or Search Guard or ReadOnlyRest or Basic Auth, uncomment the variable and configure the variable with the respective value given below:

        • # If Elasticsearch uses security or basic auth, add the security username and password here for Skedler.
          
          #skedler_elasticsearch_username: user
          #skedler_elasticsearch_password: pass    

      •   On Advanced Configuration refer to the following article Reporting.yml & ReportEngine Configuration
    • If you would like to use Internal Database as a Datastore, follow the configuration shown below,

      • Skedler uses an embedded database to store metadata and history data. The embedded database is located at,

        For linux, /var/lib/skedler/skedler.db and /var/lib/skedler/skedlerHistory.db 
        For windows, C:\skedler\skedler.db and C:\skedler\skedlerHistory.db