Frequently Asked Questions

NETWAYS Web Service (NWS) is a Software as a Service Platform which provides latest Open Source Software hosted in the cloud. NWS allows customers in an easy way to use pre-configured open source stacks called NWS-Apps.

Paying by credit card is our main payment method. If desired we offer other payment methods which require paying for 12 months in advance. For further information please get in touch with us.

Just follow the Your Apps link in the navigation bar to get to the NWS-Apps overview.

Each NWS-App provides an overview including at least Live View, Access information and FAQ. You can find all necessary links and credentials in the Access section.

We provide pre-configured Open Source applications to get your preferred tools fast and easily running. We are sorry if you have trouble with an app or a single component. Please contact service@netways.de or use our live chat and provide detailed information (at least the application url). Please keep in mind that we do not provide solutions to general issues of the provided Open Source app.

For each NWS-App we provide at least a free trial period of one month. The first time we will charge your credit card is at the end of the trial period. From that moment on we will charge your credit card in a monthly interval. For the exact date please have a look at your NWS-Apps overview. For further information have a look in the Terms of Payment.

If you want to change your password or if you have forgotten your password, just log out and follow the instructions to reset your password.

We provide a strong initial password for accessing your apps. It is in your liability to change the app passwords within each app separately. Once changed we are technically not able to retrieve your password. If necessary we integrate a technical user for accounting purposes.

To upgrade your subscription plan go to the NWS-Apps overview and follow the upgrade link belonging to the app you want to upgrade.

Downgrading your NWS-App is possible by going to the NWS-Apps overview and follow the upgrade link. There you can select a smaller plan as already chosen. Please note that you are only able to downgrade once within a billing period. Your already paid plan costs will be credited accordingly in your next invoice.

You can change or recall your payment method in your account settings. We only accept Visa and MasterCard as payment method by now. For further information have a look in the Terms of Payment.

Go to Account and choose Billing. All your bills are listed there, with an option to download.
Note: It can take up to an hour untill your bill will show up in the billing section.

You can cancel your NWS-Apps at any time, and you will continue to have access to the NWS-App through the end of your monthly billing period. To cancel your app go to the NWS-Apps overview and follow the delete link belonging to the app.

We do not provide guaranteed service level. Nonetheless we make a continuous effort to provide a highly available platform and NWS-Apps. Unavailability of your NWS-App should only occur on upgrades.

We keep track on the releases of each single software component used by the NWS-Apps. Depending on new features, bug fixes and security issues we will upgrade and restart your NWS-App. In the usual case your app will be upgraded within a couple of weeks, after the new release and upgrade path is tested and implemented.

First of all we stop the running processes. According to the specific app, we need to migrate your data or database to the new version of the application. Afterwards we start the new version of your application and reconfigure the load balancers. Meanwhile the application is not accessible, but the whole process should never last longer as a few minutes.

Each of your Apps is provided as single-tenant and started within it's own separated environment (inlcuding the network), to make sure you are the only one accessing your data.

Yes. If you need custom adjustments to your NWS-App please write to info@netways.de.

Yes. Just go to the 'Access' tab of a specific NWS-App and fill the 'CName' form. This will restart your NWS-App and within minutes your app can be accessed under the new name. Of course, the technical name will still work, too.

We do daily backups of the persistent components (e.g. databases and config files) of your NWS-Apps for recovery purposes if there are technical errors. We do not provide a backup for non-error cases.

Our datacenters are located in Nuremberg, Germany. Both are independently connected to multiple uplink carriers and fulfill highest industry standards in terms of security, connectivity and disaster prevention. One of them is ISO-27001 also certified. Additionally we are running EC2 instances at Amazon Web Services to deploy Apps (Icinga 2 Satellite) in North California and Tokyo.

Username and password will be provided in the Access tab.

Right here: Icinga 2 Documentation
You can also enable the Documentation-module inside your Icinga 2 Web by choosing Configuration from the menu on the left hand side and clicking on Modules in the drop-down menu. Now click on the module doc and change its state to enabled.

If you want to create additional user-logins for your Icinga Web 2 Interface, log in as admin and go to Settings and choose Authentication from the drop-down menu. Now click on Users in the upper menu-bar and then click the Add a New User-Button. Enter your desired username and password and click Add.

Adding services and hosts to the monitoring is done by using the Configuration. Log in to your Icinga Web 2 Interface and choose Configuration from the left side menu. Now select whatever you would like to add to your monitoring.
For a more detailed introduction to Icinga Director visit the Icinga Web 2 Director Documentation on GitHub.

Simply click on Add Agent in your App view, choose the operating system of your existing server and download the shown script. Then place it on your server and run it. The script will setup your system by installing the Icinga 2 Client and establish a secure connection to your preconfigured Icinga 2 Master stack. For monitoring your system click on Icinga 2 Web and login with your username and password.

To deploy changes in Icinga Web 2 navigate to the Configuration, choose Activity Log and click on Deploy pending changes.

To change the interval for a specific check go to Configuration / Hosts and click on the host that contains the service check you want to modify. Now select the Services tab from the top and click on the desired service. Click on Imports* then on "- click to add new one -" and select interval-10min or any other interval- template you would like to use. Finally click on Store and deploy your changes.

The nagios plugins are probably missing on the host you want to monitor. You can download them from monitoring-plugins.org or search for a specific plugin at exchange.icinga.com.

Go to Configuration, select Hosts and click on the hostname of the host you want to modify or delete. If you want to delete the host then scroll down and click Delete. If you just want to delete a service of this host click on Services on the right hand side, select the specific service and click Delete.

First you might want to check the user-templates in the Configuration. Navigate to Configuration / Users / Templates and click on the user-template. In Main properties you can add groups to the user-template and also decide if those users should receive notifications. You may add your own user-templates and specify different (notification) groups. There are some predefined groups intended for text and mail notifications from which you can choose. To apply the user template to a new user you need to go to Icinga Director / Users and click on Add. Now fill in a username and select your template at Imports. You may also assign the user to additional groups that are not listed in the user template. Finally click Store and deploy the changes.

Click on Configuration and select Notifications. You can choose from the predefined notification templates but you may also create your own templates. Configure the notification to your needs and save it by clicking on Add. Make sure to deploy your changes afterwards.

To enable or disable SMS notifications go to the Configuration and choose Notifications. Select service-sms-notification or host-sms-notification and set Disabled to No or Yes.

apt - by_ssh - cluster - cluster-zone - cpu - dhcp - dig - disk - dns - ftp - hostalive - http - icmp - imap - iostat - ldap - load - mem - mongodb - mssql_health - mysql_health - negate - ping - pop - postgres - procs - rbl - simap - smtp - spop - ssh - ssmtp - swap - tcp - udp - users - webinject - yum

apt

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "apt-on-agent" {
      import "default-service-template"
  
      check_command = "apt"
      command_endpoint = host_name
      assign where host.vars.dist == "Debian" || host.vars.dist == "Ubuntu"
  }

Weiter Informationen - Ressource

by_ssh

Currently not possible to process/show with Icinga Director at 1.2.x, unless you make usage of the Director API. The reason for this is the requirement of an own dictionary as command and arguments. But we have an example in our Blog.

Weiter Informationen - Ressource

cluster

Check command for the built-in cluster check. This check returns performance data for the current Icinga instance and connected endpoints.

Beispiel:

  apply Service "icinga cluster" {
      import "default-service-template"
  
      check_command = "cluster"
      assign where host.vars.icinga-master
  }

Weiter Informationen - Ressource

cluster-zone

Check command for the built-in cluster-zone check. On Agent servers this is a possible replacement for the hostalive check. It monitors the connection between the Agent and Master.

Beispiel:

  template Host "Host with installed Icinga2 Agent" {
      check_command = "cluster-zone"
      max_check_attempts = "3"
      check_interval = 10m
      retry_interval = 3m
  }

Weiter Informationen - Ressource

cpu

This is a plugin to monitor the CPU usage on Linux systems and the different states. It needs to be build manually. The process is simple and only basic tools and packages are needed. Additional, to the default plugins Perl modules, you need Module::Install and the basic 'make' + build tools. A detailed description is on GitHub.

Beispiel:

  object CheckCommand "cpu" {
      import "plugin-check-command"
  
      command = [ PluginDir + "/check_cpu" ]
      arguments = {
          "-c" = {
              required = true
              value = "$cpu_critical$"
          }
          "-s" = {
              set_if = "$cpu_silent$"
          }
          "-t" = "$cpu_timeout$"
          "-w" = {
              required = true
              value = "$cpu_warning$"
          }
      }
      vars.cpu_silent = false
  }
  
  
  apply Service "cpu" {
      import "default-service-template"
  
      check_command = "cpu"
      vars.cpu_critical = "90"
      vars.cpu_silent = "1"
      vars.cpu_warning = "2"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

dhcp

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "dhcp-on-agent" {
      import "default-service-template"
  
      check_command = "dhcp"
      command_endpoint = host_name
      vars.dhcp_interface = "enp0s1"
      vars.dhcp_requestedip = "10.11.12.123"
      vars.dhcp_serverip = "10.11.12.100"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

dig

Provided by the package : monitoring-plugins-standard

Beispiel:

  apply Service "dig" {
      import "default-service-template"
  
      check_command = "dig"
      vars.check_address = "ns1.netways.de"
      vars.dig_critical = "4"
      vars.dig_expected_address = "185.11.252.146"
      vars.dig_lookup = "nws.netways.de"
      vars.dig_timeout = "5"
      vars.dig_warning = "2"
      assign where host.name == "DNS-Master"
  }

Weiter Informationen - Ressource

disk

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "disk-on-agent" {
      import "default-service-template"
  
      check_command = "disk"
      command_endpoint = host_name
      vars.disk_cfree = "8%"
      vars.disk_errors_only = true
      vars.disk_ignore_reserved = true
      vars.disk_inode_cfree = "8%"
      vars.disk_inode_wfree = "15%"
      vars.disk_megabytes = true
      vars.disk_stat_remote_fs = true
      vars.disk_wfree = "15%"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

dns

Provided by the package : monitoring-plugins-standard

Beispiel:

  apply Service "dns" {
      import "default-service-template"
  
      check_command = "dns"
      vars.dns_expected_answer = "185.11.252.146"
      vars.dns_lookup = "nws.netways.de"
      assign where host.name == "DNS-Master"
  }

Weiter Informationen - Ressource

ftp

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets the default port, expect and quit values

Beispiel:

  apply Service "ftp" {
      import "default-service-template"
  
      check_command = "ftp"
      vars.ftp_ctime = "6"
      vars.ftp_timeout = "8"
      vars.ftp_wtime = "3"
      assign where "File-Transfer" in host.vars.type
  }

Weiter Informationen - Ressource

hostalive

This command make usage of check_ping and does not require any adjustments in the parameters. All values are correclty set to make sure that the host is up or down. It is normaly used in the default 'generic-host' template.

Beispiel:

  template Host "Host without installed Icinga2 Agent" {
      check_command = "hostalive"
      max_check_attempts = "3"
      check_interval = 10m
      retry_interval = 3m
  }

Weiter Informationen - Ressource

http

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "http" {
      import "default-service-template"
  
      check_command = "http"
      vars.http_onredirect = "follow"
      vars.http_string = "NETWAYS"
      vars.http_uri = "/kontakt/impressum/"
      vars.http_vhost = "www.netways.de"
      assign where host.vars.type == "Web-Server"
  }

Weiter Informationen - Ressource

icmp

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "icmp" {
      import "default-service-template"
  
      check_command = "icmp"
      assign where host.address != ""
  }

Weiter Informationen - Ressource

imap

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets the default port, expect and quit values

Beispiel:

  apply Service "imap" {
      import "default-service-template"
  
      check_command = "imap"
      vars.imap_ctime = "6"
      vars.imap_timeout = "8"
      vars.imap_wtime = "3"
      assign where "IMAP Accounts" in host.vars.type
  }

Weiter Informationen - Ressource

iostat

This plugin is a normal Shell script and should not have any more requirements. Used tools like iostat and bc will be installed on any modern distribution.

Beispiel:

  template Service "iostat-on-agent" {
      import "default-service-template"
  
      check_command = "iostat"
      command_endpoint = host_name
      vars.iostat_disk = "sdb"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

ldap

Provided by the package : monitoring-plugins-standard

Beispiel:

  apply Service "ldap - sso" {
      import "default-service-template"
  
      check_command = "ldap"
      vars.ldap_base = "dc=your,dc=company,dc=com"
      vars.ldap_bind = "cn=service,ou=tools,dc=your,dc=company,dc=com"
      vars.ldap_pass = "secret"
      vars.ldap_v3 = true
      assign where host.sso_dc
  }

Weiter Informationen - Ressource

load

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "load-on-agent" {
      import "default-service-template"
  
      check_command = "load"
      command_endpoint = host_name
      vars.load_cload1 = "5"
      vars.load_cload15 = "3"
      vars.load_cload5 = "4"
      vars.load_percpu = true
      vars.load_wload1 = "4"
      vars.load_wload15 = "2"
      vars.load_wload5 = "3"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

mem

The plugin mem is used for gathering information about memory usage on linux and unix hosts.
It is able to count cache memory as free when comparing it to the thresholds.
The code is provided by Justin Ellison on https://github.com.

Beispiel:

  apply Service "mem-on-agent" {
      import "default-service-template"
  
      check_command = "mem"
      command_endpoint = host_name
      vars.mem_cache = true
      vars.mem_critical = "99"
      vars.mem_used = true
      vars.mem_warning = "95"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

mongodb

Provided by the package : nagios-plugins-contrib and utilises Python PyMongo

Beispiel:

  apply Service "mongodb - DocType size" {
      import "default-service-template"
  
      check_command = "mongodb"
      vars.mongodb_action = "database_indexes"
      vars.mongodb_critical = "150"
      vars.mongodb_database = "DocType"
      vars.mongodb_port = "27017"
      vars.mongodb_warning = "75"
      assign where host.mongodb && "DocType" in host.mongodb.dbs
  }

Weiter Informationen - Ressource

mssql_health

The plugin can be obtained from the ConSol Homepage or on GitHub from Gerhard Lausser

Beispiel:

  apply Service "mssql_health" {
      import "default-service-template"
  
      check_command = "mssql_health"
      vars.mssql_health_critical = "512"
      vars.mssql_health_mode = "database-free"
      vars.mssql_health_name = "MediaData"
      vars.mssql_health_units = "MB"
      vars.mssql_health_warning = "2048"
      assign where host.os == "Windows" && host.type == "MediaDB"
  }

Weiter Informationen - Ressource

mysql_health

The current ITL definition also includes parameters from the new beta 3 Version. This beta can be obtained from the ConSol Homepage.
Below is a list of the new options:

blacklist
commit
criticalx
environment
extra-opts
isvalidtime
ookback
method
mitigation
morphmessage
morphperfdata
multiline
name3
negate
nooffline
notemp
report
selectedperfdata
statefilesdir
warningx
with-mymodules-dyn-dir

Beispiel:

  apply Service "icinga - inactive objects" {
      import "default-service-template"
  
      check_command = "mysql_health"
      vars.mysql_health_critical = "2000"
      vars.mysql_health_database = "icinga"
      vars.mysql_health_hostname = "database-cluster-master"
      vars.mysql_health_mode = "sql"
      vars.mysql_health_name = "select count(*) from icinga_objects where is_active = 0"
      vars.mysql_health_name2 = "inactive objects"
      vars.mysql_health_password = "secret"
      vars.mysql_health_port = "3306"
      vars.mysql_health_username = "admin"
      vars.mysql_health_warning = "1500"
      assign where host.name == "database-cluster-master"
  }

Weiter Informationen - Ressource

negate

Currently not possible to process/show with Icinga Director at 1.2.x, unless you make usage of the Director API. The reason for this is the requirement of an own dictionary as command and arguments. This is the same as by_ssh, like shown in our blog

Weiter Informationen - Ressource

ping

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "ping" {
      import "default-service-template"
  
      check_command = "ping"
      assign where host.name
  }

Weiter Informationen - Ressource

pop

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets the default port, expect and quit values

Beispiel:

  apply Service "pop" {
      import "default-service-template"
  
      check_command = "pop"
      vars.pop_ctime = "6"
      vars.pop_timeout = "8"
      vars.pop_wtime = "3"
      assign where "POP Accounts" in host.vars.type
  }

Weiter Informationen - Ressource

postgres

The plugin can easy be build via Perl:

perl Makefile.PL INSTALLSITESCRIPT=/PATH/TO/YOUR/PLUGINS
make
make install

But it is recommended to have at least the Postgres client installed for all tests.

Beispiel:

  apply Service "postgres" {
      import "default-service-template"
  
      check_command = "postgres"
      vars.postgres_action = "backends"
      vars.postgres_critical = "95%"
      vars.postgres_dbname = "sessions"
      vars.postgres_host = "psql-master"
      vars.postgres_warning = "90%"
      assign where host.name == "psql-master"
  }

Weiter Informationen - Ressource

procs

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "icinga vsz" {
      import "default-service-template"
  
      check_command = "procs"
      command_endpoint = host_name
      vars.procs_argument = "daemon"
      vars.procs_command = "icinga2"
      vars.procs_critical = "4000000"
      vars.procs_metric = "VSZ"
      vars.procs_vsz = "nagios"
      vars.procs_warning = "2500000"
      assign where host.vars.has_agent
  }

Weiter Informationen - Ressource

rbl

Provided by the package : nagios-plugins-contrib

Beispiel:

  apply Service "rbl listing" {
      import "default-service-template"
  
      check_command = "rbl"
      vars.rbl_critical = "4"
      vars.rbl_server = "['zen.spamhaus.org', 'bl.spamcop.net', 'ix.dnsbl.manitu.net', 'cbl.abuseat.org','dnsbl.sorbs.net']"
      vars.rbl_timeout = "45"
      vars.rbl_warning = "2"
      assign where host.mailserver
  }

Weiter Informationen - Ressource

simap

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets SSL usage, the default port, expect and quit values

Beispiel:

  apply Service "simap" {
      import "default-service-template"
  
      check_command = "simap"
      vars.simap_ctime = "6"
      vars.simap_timeout = "8"
      vars.simap_wtime = "3"
      assign where "IMAP Accounts SSL" in host.vars.type
  }

Weiter Informationen - Ressource

smtp

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets the default port, expect and quit values

Beispiel:

  apply Service "smtp" {
      import "default-service-template"
  
      check_command = "smtp"
      vars.smtp_ctime = "6"
      vars.smtp_timeout = "8"
      vars.smtp_wtime = "3"
      assign where "SMTP" in host.vars.type
  }

Weiter Informationen - Ressource

spop

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets SSL usage, the default port, expect and quit values

Beispiel:

  apply Service "spop" {
      import "default-service-template"
  
      check_command = "spop"
      vars.spop_ctime = "6"
      vars.spop_timeout = "8"
      vars.spop_wtime = "3"
      assign where "POP Accounts SSL" in host.vars.type
  }

Weiter Informationen - Ressource

ssh

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "ssh" {
      import "default-service-template"
      check_command = "ssh"
      vars.ssh_port = "22"
      vars.ssh_timeout = "5"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

ssmtp

Provided by the package : monitoring-plugins-basic, it is an alias for check_tcp which sets the default port, expect and quit values

Beispiel:

  apply Service "ssmtp" {
      import "default-service-template"
  
      check_command = "ssmtp"
      vars.ssmtp_ctime = "6"
      vars.ssmtp_timeout = "8"
      vars.ssmtp_wtime = "3"
      assign where "SMTP SSL" in host.vars.type
  }

Weiter Informationen - Ressource

swap

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "swap" {
      import "default-service-template"
  
      check_command = "swap"
      command_endpoint = host_name
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

tcp

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "http response" {
      import "default-service-template"
  
      check_command = "tcp"
      vars.tcp_address = "www.netways.de"
      vars.tcp_certificate = "60"
      vars.tcp_ctime = "1"
      vars.tcp_port = "443"
      vars.tcp_timeout = "2"
      vars.tcp_wtime = "0.5"
      assign where host.vars.type == "Web-Server"
  }

Weiter Informationen - Ressource

udp

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "udp-expect" {
      import "default-service-template"
      check_command = "udp"
      vars.udp_expect = "Expected Return String"
      vars.udp_port = 1234
      vars.udp_send = "Service Send String"
      assign where "udp-expect" in host.vars.services
  }

Weiter Informationen - Ressource

users

Provided by the package : monitoring-plugins-basic

Beispiel:

  apply Service "users-on-agent" {
      import "default-service-template"
  
      check_command = "users"
      command_endpoint = host_name
      vars.users_cgreater = "50"
      vars.users_wgreater = "75"
      assign where host.vars.os == "Linux"
  }

Weiter Informationen - Ressource

webinject

Provided by the package : nagios-plugins-contrib
It requires also the WebInject Perl module.

Beispiel:

  apply Service "custom site check" {
      import "default-service-template"
  
      check_command = "webinject"
      vars.webinject_config_file = "/usr/share/icinga2/webinject/config.xml"
      vars.webinject_testcase_file = "/usr/share/icinga2/webinject/customer-a/case1.xml"
      assign where host.vars.customer == "A" && host.vars.type == "WebServer"
  }

Weiter Informationen - Ressource

yum

The plugin is written in Python and the ITL fills all mostly needed values. It can be found on GitHub.

Beispiel:

  apply Service "yum-on-agent" {
      import "default-service-template"
  
      check_command = "yum"
      command_endpoint = host_name
      assign where host.vars.dist == "RedHat" || host.vars.dist == "CentOS"
  }

Weiter Informationen - Ressource

You can find all available plugins listed here. If your desired plugin is not available, we can add it for you. Get in touch with us.

You are able to get your notifications in your Slack workspace. To do so, you just need to configure a few things:

1) Go to Configuration/Commands
2) Open command-slack-host/command-slack-service and open the drop-down Custom properties
3) Fill in the slack_channel you want to use (you have to create one first in your Slack workspace)
4) Fill in the slack_webhook_url. You can get your webhook url from your Slack-account settings
5) Create a new user in Configuration/User and add him to the two groups for Slack-Message on critical hosts/services. Also give him the user template user-template in Imports
6) Add the states you want to receive notifications for to the Configuration / User/Contacts / User-template / modify / State and transition type filters field
7) Deploy your changes in the Configuration/Deployments

You can integrate Icinga2 Notifications automatically in your Rocket.Chat app. All you have to do, is to start both apps. You can change the types of alerts you want to receive in "Configuration / Notifications / Notifications".

Right here: Icinga 2 Documentation
You can also enable the Documentation-module inside your Icinga 2 Web by choosing Configuration from the menu on the left hand side and clicking on Modules in the drop-down menu. Now click on the module doc and change its state to enable.

Go to Account and choose Billing. All your bills should be listed there with an option to download them.
Note: It can take up to an hour after your purchase until your bill will show up in the billing section.

Please have a look at the common mistakes below.

Error: Object 'master' of type 'Zone' does not exists.

Please ensure you have a valid master configuration including a zone named master. For setups initialized with the icinga2 node wizard set the ZoneName in /etc/icinga2/constants.conf to:

You will find detailed User Guides in the Rocket.Chat Docs

There are different ways to add users to your Rocket.Chat server.
Manually through the Administration/Users section:
Click on your username and open the Administration panel. Then choose Users and create a new user by clicking on '+' and enter the desired user credentials.
Enabling the registration form:
To enable the registration form open the Administration panel and choose Accounts. Expand the Registration section on the bottom and set Registration Form either to Public or to Secret URL. If you are using Secret URL then you may also change Registration Form Secret URL to a desired string. Then scroll down and hit Save Changes. To get to the registration form you simply add /register/"your-string" to your Rocket.Chat link.

Rocket.Chat is preconfigured to allow only specified file types. You may change the allowed file types at Administration/File Upload.

The Livechat feature is only available in the 'Advanced' and 'Premium' plans and enabled by default.
To enable/disable it: log in with your credentials, click on your username in the upper left, choose Administration, go to Livechat, and change Livechat enabled. Scroll down and click save changes. Close the administration screen on the upper left and reload the page in your browser. To make Livechat available on your website you will have to make sure that the Livechat switch on the left hand side is set to green. Then you'll have to click on the down-arrow next to your username and choose Livechat and then Installation. Now follow the instructions on this page. You can use the same Java Script for embedding the Livechat feature on multiple websites. We have no hard limits here. Further Livechat related guides can be found here.

If you have bought an Icinga 2 Master and a Rocket.Chat this will be detected by our NWS system and it will automatically connect both apps. The Icinga 2 Master will be set up to send notifications to your Rocket.Chat server. The notifications will then appear as messages from icinga-user in the Icinga2 channel. Also your admin user will be added automatically to this channel.

This admin-account is from NWS. Its sole purpose is to monitor the user limit. NOTE: Changes to this account will be reset by the NWS system.

You will need a compatible camera and microphone. Also note that Safari and Edge are not supported at the moment. Please use the latest Chrome or Firefox version instead. To check if your setup is compatible you may use this online device compatibility verification tool. All tests should pass except for IPV6 support.

Make sure you have this feature enabled in the administration settings. Choose Accounts and scroll down and expand Registration, there you will find the settings for email verification. NOTE: Turning on email verification will only allow users with verified accounts to login. So before you change to email verification make sure your admin account has verified checked in user settings. Otherwise you might get locked out of your Rocket.Chat server.

For screensharing you will need to install a browser add-on. Currently there are add-ons for Chrome and Firefox available.

Go to Account and choose Billing. All your bills should be listed there with an option to download them.
Note: It can take up to an hour until your bill will show up in the billing section.

If you created a custom domain name for your Rocket.Chat app and you try to access it from your browser using the new domain name, you may encounter some problems. For example if you upload pictures to a channel you will notice that you don't get any previews and you will get an HTTP 403 Error if you try to open the picture. In order to solve this problem you have to go to the Rocket.Chat settings and choose General from the left hand side. Now enter your custom domain name in the Site URL field and click SAVE CHANGES in the upper right corner. Now reload the page and you should see the previews and pictures in the channel.

The Version 0.62.0 of Rocket.Chat is not compatible with the Safari 10.1 of MacOS Sierra. Please use another browser or update to a newer version.

You can integrate Icinga2 Notifications automatically in your Rocket.Chat app. All you have to do, is to start both apps. You can change the types of alerts you want to receive in "Configuration / Notifications / Notifications".

You will find a detailed User Manual at the Nextcloud Docs

Uploading files through the web interface will be done with the Files app. Above the list of your files there is a button with a '+' symbol. Click on it and select Upload. Then select the file(s) you would like to upload and click Open.

To create a new folder, again click on the '+' button on the top but this time choose Folder. Now enter the desired folder name and hit enter on your keyboard.

This happens, because your files are uploaded to the S3 storage in the background. This can probably take a while, depending on how much data you are uploading. Nextcloud itself can't calculate how long this will take.

Log in as admin and click on your username in the upper right then select Users. To add a group click on + Add group in the left column, fill in the name (for example 'users') and hit enter or click on '+'. To create a new user simply fill in the username and password in the fields on the top then select the group(s) you would like this user to be a member of and click Create.
Further information about user management in Nextcloud can be found here.
Note: please keep in mind that there are user limits for some plans.

To share a file or a folder you will have to open the Files app from the app menu. All your files will be listed there. Notice that each file has a symbol of three connected dots shaped like a triangle. If you click on this symbol you will see that the sharing options for this file pop up in a separate column on the right side. Now you can either share the file/folder with other users or groups on your Nextcloud server or you can enter an email address to send an email to the person you would like to share this file with. Just enter the username, groupname or email address in the field below Sharing and hit enter on your keyboard. But instead you may also create a link that you can copy and then share with other people. Just click on the Share link checkbox. The link will then be generated and displayed below. You also have some options you can set for this link, like setting an expiration date or protecting it by password.

If you want to disable sharing for a file or folder just go to the sharing column (as mentioned above) and remove the users/groups/email addresses by clicking on the three dots next to the edit option and selecting Unshare.
The link sharing can be disabled by unchecking the Share link checkbox.
To get a list of all the files and folders you are currently sharing in your files app, select Shared with others in the column on the left hand side.

To delete a file or multiple files at once, just go with the cursor over the file name. Click on the checkbox next to the thumbnail of the file. Then choose Delete on the right hand side. The file(s) will be moved to the trash bin. In order to permanently delete files you'll have to clear the trash bin. Click on Deleted files located down on the left hand side. Then once again select the files you want to permanently remove from your Nextcloud by marking the checkboxes and clicking on Delete.

To connect to your Nextcloud server via WebDAV you might need a WebDAV client for your PC/Mac. But many Operating Systems already have WebDAV capability built in. You may use your favorite online search engine to find a suitable WebDAV solution for your system. In order to connect through WebDAV you'll need the WebDAV link of your Nextcloud server. In the web interface of Nextcloud open up the Files app and select Settings on the bottom left. Now copy the link displayed below. You might have to change the leading part from 'https://' to 'davs://' if it does not work right away. When prompted, insert your username and password of your Nextcloud user.

To be able to manage file access you need to enable the Files Access Control app. Select Apps from your app menu and navigate to the Not enabled section. Now enable File access control. In your Admin panel (click on your username in the upper right and select 'Admin') you'll now find the Files access control section.
More information on how to configure file access can be found here.

First you'll have to enable External storage support. Log in with your admin user, click on Files in the upper left and select Apps. Now click on the Not enabled section on the left and then enable External storage support. Now click on your username in the upper right and select Admin. Then choose External storage from the menu on the left. Select the storage type you would like to add and fill in the authentication credentials. For some external storage types like Dropbox you may need to generate an App key and App secret.
For further detailed instructions on how to configure the different storage types read this section of the manual.

The update/upgrade process will be done by the NWS platform as soon as the new Nextcloud version has been tested and confirmed to be working properly with our infrastructure. We'll announce upgrade periods by email. Your Nextcloud server will then be upgraded during a restart which should not take longer than a couple of minutes.

The nws-admin account on your Nextcloud server allows the NWS platform to keep track of how many user accounts you have. Please do not delete the nws-admin or change any credentials of this account for your own convenience. Our automated tasks will notice if the nws-admin was modified and will trigger a restart of your Nextcloud app to reset the nws-admin.

If you would like to enable encryption, there are a few things you should know. Home storage encryption is not completely supported at the moment. You can enable home storage encryption but you may notice that you won't get any previews and thumbnails for videos and pictures. For external storage like Dropbox or Amazon S3 encryption works without any issues.

To get access trough iFrame to your Nextcloud app, you have to give domains and IPs free. Just set them in the "CSP" tab and seperate them with new lines.
You will have to specify them the folling way:
http://yourdomain.com | https://yourdomain.com | http://yourdomain.com:port | https://yourdomain.com:port

The | (pipe) stands for "or" in this example. Please sperate the domains/IPs with new lines in the CSP tab.

You will find detailed User Guides in the Gitlab CE documentation.

Username and url are provided in the Access tab. You have to set the password for the root user at your initial login.

We suggest taking a value between 2 and 4 days, depending on how fast your data is growing. You can change for this, the following parameter in Gitlab:
Default artifacts expiration

At the moment it is not possible to use ssh to access your git repository. For an easy access we recommend to configure your local git credential helpers.

• HTTPS is compatible, accessible and common traffic on firewalls and gateways. Even if you use a HTTP-Proxy within your internal network your code is still available.
• The git credential helpers can be easily integrated with your local keyring to save your credentials in a secure manner.
• TLS verifies the server you are connecting.
• GitLab-CE with HTTPS provides to use and generate api tokens.

NWS is using SNI for SSL connections. Therefore you need to make sure to always use correct and up-to-date versions of OpenSSL no matter if you want to use git on Mac, Linux or Windows. For Windows, you can alternatively use the native Windows Secure Channel library. It can be directly selected in the git installer:

You will find detailed User Guides in the GitLab EE documentation.

Username and url are provided in the Access tab. You have to set the password for the root user at your initial login.

We suggest taking a value between 2 and 4 days, depending on how fast your data is growing. You can change for this, the following parameter in Gitlab:
Default artifacts expiration

At the moment it is not possible to use ssh to access your git repository. For an easy access we recommend to configure your local git credential helpers.

• HTTPS is compatible, accessible and common traffic on firewalls and gateways. Even if you use a HTTP-Proxy within your internal network your code is still available.
• The git credential helpers can be easily integrated with your local keyring to save your credentials in a secure manner.
• TLS verifies the server you are connecting.
• GitLab-CE with HTTPS provides to use and generate api tokens.

NWS is using SNI for SSL connections. Therefore you need to make sure to always use correct and up-to-date versions of OpenSSL libraries no matter if you want to use git on Mac, Linux or Windows. For Windows, you can alternatively use the native Windows Secure Channel library. It can be directly selected in the git installer:

You can purchase a Gitlab Enterprise Edition license at Gitlab.com or within your Gitlab EE App. (Administration --> License)

Yes, just enter it in your Gitlab EE App (Administration --> License).

You will find detailed user guides in the SuiteCRM documentation.

Username and url are provided in the Access tab.

Yes! It's possible to add SuiteCRM addons via the admin panel.

Yes! Your data is very important to us - if you need help downloading your data from SuiteCRM, please contact our support via livechat.

It's possible to import data from other systems via the importer tool in the admin panel.

No, we don't provide that kind of service for security reasons.

The NWS WebAccelerator provides a fast cache for the static content of your web site to speed up the loading time of your web pages. To use the WebAccelerator you have to provide the domain of your web site and the corresponding TLS/SSL certificate and you have to redirect the DNS records of your domain to 185.11.252.146. Henceforward the static content of your web page is delivered through the WebAccelerator and only the dynamic content is served from your web servers. For best results we recommend to make your static content (e.g. images and css files) available on a own subdomain (e.g. static.example.com) and set the DNS records for the subdomain to 185.11.252.146.

You can provide your own maintenance page for the case that your web servers are not available. Please upload the content packed in a .tar or .zip archive. Please ensure that there is an index.html in the top directory. To link external css or image files use relative paths within your index.html and add them to the archive.

Yes! Just go to the settings panel and hit the 'Clear Cache' button on the bottom of the page.

TTL stands for time to live and defines how long your static content is kept in the cache (e.g. 10m, 2h, 8d)

You will find a detailed User Manual at the User Manual as well as an Administration Manual at the Request Tracker Wiki

Short explanation why you should consider setting up Request Tracker to send/receive mails using an existing mail account:
In RT you normally have one or multiple queues where your customer's requests arrive via e-mail and automatically trigger creation of a new ticket. Most businesses would want to use their own e-mail domain for referring their customers to their ticket system.

After your Request Tracker App has created successfully, please click on Show and head over to the Config tab. Now scroll down to Your Mail Configuration. Please fill in all the fields with your configuration details and choose the radio buttons that correspond to your environment. On this tab, you can also choose comment or correspond in the section Queue Action. This determines how incoming mails are handled - they will either be marked as comment or as correspondence. By clicking the Save Button, your values will be handed over to the app. Please consider that filling in these details is necessary for your RT to start as there are no default values for IMAP/POP3 at the moment. Furthermore, any incoming mail that creates a new ticket will generate an autoresponse. You can edit this behaviour after logging into your RT as administrator and then by clicking on Admin > Queues > Select. There you need to choose the queue you want to edit and then click on Scrips > Select. Now you can for example disable the sending of autoresponses.

Short version: no.
But if you provided Your Mail Configuration, then you should enter the e-mail address of the e-mail account you want to use in the Outgoing E-Mail Address field.

To get there follow the steps below:
After your Request Tracker App has created successfully, please click on Show in order to get forwarded to the app's details page. There you have different tabs you can choose.
In the tab Access you will find a field where you can enter your preferred CNAME for your product.
In the tab Config you have the possibility to customize RT-Name, mail addresses, timezone, the name of your organization as well as the Mail Configuration of your RT. By clicking the Save Button, your values will be handed over to the app. All these fields can be accessed and edited at any time later. The following applies to all fields except for your mail configuration: If nothing is entered, the app will use its given default values. When emptying the fields, the app reverts back to its default values.

For any action regarding Users and Groups, you need to login as administrator. Then you should expand the Admin tab in the navigation bar and click on either Users or Groups. For creating new Users or Groups, you can click on Create or for editing existing Users or Groups you can choose Select.
Further information about user management in Request Tracker can be found here.
Note: please keep in mind that there are user limits for some plans.

For any action regarding ticket queues, you need to login as administrator. Then you should expand the Configuration tab in the navigation bar and click on either Queues. For creating new queues, you can click on New Queue or for editing existing queues you can choose the name of the queue in question. Furthermore, you can add watchers to the queue. So again, go to Configuration, then to Queues and lick on the name of the queue you want to add watchers to. Then click on Watchers and add the desired user. For removing watchers, just uncheck the box next to the user's name.

The update/upgrade process will be done by the NWS platform as soon as the new Request Tracker version has been tested and confirmed to be working properly with our infrastructure. We'll announce upgrade periods by email. Your Request Tracker app will then be upgraded during a restart which should not take longer than a couple of minutes.

The nws-api account on your Request Tracker app allows the NWS platform to keep track of how many user accounts you have. Please do not delete the nws-api or change any credentials of this account for your own convenience. Our automated tasks will notice if the nws-api was modified and will trigger a restart of your Request Tracker app to reset the nws-admin.

Go to your Apps, then click on the Access Tab, where your credentials are stored.

OpenStack differs between Emphemeral Disks, Images and Volumes.
A volume is just a RBD (Rados Block Device) which resides in our Ceph cluster and can be attached to your instances.
A image is an exact replica of the contents of the disks.
A ephemeral disk is a temporary storage. Its data will be lost, when the instance which it is attached to.

When you trigger a migration a instance will be moved from one hypervisor to another

Live migration refers to the migration while the instance up and running. Clients and applications will not be disconnected.

Normal migration will only work, when the instance was shut down before.

Please note, that you can't migrate the instances by your own. You will have to contact the support team for that.

• A normal virtual machine has a Emphemeral Disk underneath. The disk image on the other side, is just a Local Storage image of your root disk and can't be used for Live Migration.
• A Volume which is attached to a instance, will not be automatically deleted if the instance is deleted. "Live migration" between hypervisors is supported.

Emphemeral		Volume
Pros automatically deleted/created higher IOPs than the volume Snapshots Management in Horizon GUI Cons no "live Migration" possible		Pros not automatically deleted Snapshots backups for ManagedVM customers "Live Migration" between hypervisors Cons IOPs are moderate and just for normal workload

While creating an instance, choose Yes under the Create New Volume Question (Launch Instance Dialog).

If it comes to "Security Groups" then you should think about it as firewall rules/policies, which can limit for expamle the traffic to your instances. You can create as many security groups as you need.

You can combine one or more rules to just one security group.

Security groups can always be attached/detached from a running instance, this has no penalty on your traffic.

Navigate to your instances menu on the left side. Open the action menu for the distance you want to interact with. (Dropdown on the right side)

Hit the Edit Security Groups entry which will bring up a new dialog..

Here you can add your security groups to your instance. When you finished editing, just save your changes.

A Floating IP is an IP address that can be instantly moved from one instance to another.

The server itself doesn't know about this IP, but all traffic will be automatically routed trough this IP to the server.

Just add a Floating IP (description above) to your instance. This will allocate a new IP from our public network and route all incommig traffic to the instance where the IP is attached to.

Don't forget to add a security group (to the server). By default a security group called default is attached, which simply allows all traffic.

The first time you create a virtual machine you are able to add one or more SSH Public Keys (also known as Key Pairs) to your instance. After creation it's currently not possible to add another key to your instances, so be aware of that.

New keys can be added/created in the Compute/Keypairs tab.

First ensure that you know what subnet your network has. You can determine this if you open the Network Topology Overview.

Next go to VPN overview and create a IKE configuration and safe your settings. (on some devices like Cisco or HP Router this is also known as Phase 1).

Poceed with the IPSec configuration in the tab IPsec Policies (on some Devices like Cisco or HP Router this is known as Phase 2)

Create the Tunnel Service itself in VPN Services.

Define the subnets of remote and local sites. To do so add a endpoint in the Endpoint Groups tab

Now create the site connection in the IPsec Site Connections. This task may fail if there is an error in the previous dialogs. If you're stuck or struggling with this, go back to the previous step and check if there is something wrong.

OpenStack has at this time of writing a bug, because he ignores the dropdown decision of Endpoint Groups, which means you have to add the subnet manually in the textfield Remote peer Subnet(s)

You can now see an entry, which means the Tunnel is Up and ready to use.

No. OpenStack just supports Site-to-site IPSec VPNs at the moment.

You will find a detailed user manual at the Horizon Docs