Failures for uptime monitors are denoted by NOK (“Not OK”) events. Below is brief description of possible common NOK events for all types of Uptime Monitors currently supported by Monitis.
HTTP
- Failed to connect to the server
- No response from the server within the set timeout
- DNS resolving error
- HTTP error
- Network or connection error
- Connection closed by server
- Basic authentication failed
- Content matching failure
HTTPS
- Failed to connect to the server.
- No response from the server within the set timeout
- DNS resolving error
- HTTP error
- Network or connection error
- Connection closed by server
- Basic authentication failed
- Content matching failure
- SSL version not supported by user’s server
FTP
- Failed to connect to the server
- No response from the server within the set timeout
- SSL version not supported by user’s server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
Ping
- No response from the server within the set timeout
- Count of lost packets is more than 3
DNS
- Failed to connect to the server
- Failed to resolve to expected IPs
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- No response from the server within the set timeout
- Connection error
- Connection closed by server
SSH
- Failed to connect to the server
- No response from the server within the set timeout
- Network or connection error
- Connection closed by server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
MySQL
- No response from the server within the set timeout
- Connection error
- Wrong URL
- Wrong database
- Wrong credentials
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
TCP
- Failed to connect to the server
- No response from the server within the set timeout
- Network or connection error
- Connection closed by server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
- SSL version not supported by user’s server
UDP
- No response from the server within the set timeout
- Network or connection error
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
POP3
- Failed to connect to the server
- No response from the server within the set timeout
- SSL version not supported by user’s server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
IMAP
- Failed to connect to the server
- No response from the server within the set timeout
- SSL version not supported by user’s server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
SMTP
- Failed to connect to the server
- No response from the server within the set timeout
- SSL version not supported by user’s server
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- DNS resolving error
SIP
- No response from the server within the set timeout
- Network or connection error
- Permission error (server behind firewall, Monitis IPs not whitelisted, etc)
- Monitor sends OPTIONS message and waits for response. If the response is < 200, then we wait for next response. If the response is 200, 401, 403, 404, 405, 407, 408, 470, then it is OK, else it is NOK.
SOAP
- Failed to connect to the server.
- No response from the server within the set timeout
- DNS resolving error
- HTTP error
- Network or connection error
- Connection closed by server
- Basic authentication failed
- Content matching failure
- SSL version not supported by user’s server
See also HTTP Response Codes for information about what HTTP Response Codes are considered NOK events by Monitis.