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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
The plugin can easy be build via Perl:
perl Makefile.PL INSTALLSITESCRIPT=/PATH/TO/YOUR/PLUGINS
make
make install
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Configuration/Commands
command-slack-host/command-slack-service
and open the drop-down Custom properties
slack_channel
you want to use (you have to create one first in your Slack workspace)slack_webhook_url
. You can get your webhook url from your Slack-account settingsConfiguration/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
Configuration / User/Contacts / User-template / modify / State and transition type filters
fieldConfiguration/Deployments
/* Our local zone name. */
const ZoneName = "master"
http://yourdomain.com | https://yourdomain.com | http://yourdomain.com:port | https://yourdomain.com:port
Default artifacts expiration
Fedora:
$ git config --global credential.helper /usr/libexec/git-core/git-credential-gnome-keyring
Fedora 27+:
git config --global credential.helper /usr/libexec/git-core/git-credential-libsecret
Ubuntu/Debian:
$ sudo apt-get install libgnome-keyring-dev
$ git config --global credential.helper /usr/share/doc/git/contrib/credential/gnome-keyring/git-credential-gnome-keyring
$ git config --global core.askpass /usr/bin/ksshaskpass
$ git config --global credential.helper manager
$ git config --global credential.helper osxkeychain
$ git config --global credential.helper store
$ git config --global credential.helper cache
Default artifacts expiration
Fedora:
$ git config --global credential.helper /usr/libexec/git-core/git-credential-gnome-keyring
Ubuntu/Debian:
$ sudo apt-get install libgnome-keyring-dev
$ git config --global credential.helper /usr/share/doc/git/contrib/credential/gnome-keyring/git-credential-gnome-keyring
$ git config --global core.askpass /usr/bin/ksshaskpass
$ git config --global credential.helper manager
$ git config --global credential.helper osxkeychain
$ git config --global credential.helper store
$ git config --global credential.helper cache
Go to your Apps, then click on the Access Tab, where your credentials are stored.
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.
Emphemeral |
Volume |
|
Pros
Cons
|
Pros
Cons
|
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.