Troubleshooting » History » Version 2
Version 1 (Luke Murphey, 03/20/2014 05:40 PM) → Version 2/11 (Luke Murphey, 05/19/2016 05:36 PM)
h1. Troubleshooting
Below are some pointers to help in debugging the application:
h2. Search for modular input errors
Run a search for the following and see if the logs indicate a problem with the modular input:
<pre>
index=_internal sourcetype=web_availability_modular_input
</pre>
h2. Search for REST handler errors
Run a search for the following and see if the logs indicate a problem with the REST handler:
<pre>
index=_internal source=*website_monitoring_rest_handler.log
</pre>
h2. Input fails and generates a "ConnectionError"
This can happen when the following is
# The IP address is invalid (if referring to the host by IP)
# The domain name cannot be resolved
# The port number provided is invalid (if a port is specified)
# Network connectivity is lost or a firewall blocks the connection
Below are some pointers to help in debugging the application:
h2. Search for modular input errors
Run a search for the following and see if the logs indicate a problem with the modular input:
<pre>
index=_internal sourcetype=web_availability_modular_input
</pre>
h2. Search for REST handler errors
Run a search for the following and see if the logs indicate a problem with the REST handler:
<pre>
index=_internal source=*website_monitoring_rest_handler.log
</pre>
h2. Input fails and generates a "ConnectionError"
This can happen when the following is
# The IP address is invalid (if referring to the host by IP)
# The domain name cannot be resolved
# The port number provided is invalid (if a port is specified)
# Network connectivity is lost or a firewall blocks the connection