Preferences:Common Properties:Watch Types

From WebWatchBotWiki
Jump to: navigation, search
 Share 

Description

The "Watch Types" section provides configuration options for different Watch Types.

preferences_watch_items.gif

Fields And Buttons

HTTP/HTTPS

  • User Agent:
    • User Agent WebWatchBot should use when downloading a page. This setting only applies to HTTP and HTTPS watch types. This setting may affect how a web page is virtually displayed if a web page changes output based on the user agent.
  • Simulate HTTP Threads:
    • The number of threads to simulate for downloading images. Web browsers can use multiple threads to download images simultaneously to increase performance. To simulate a user experience, this setting is used. The default value is 3. To capture a total download response time regardless of the number of threads, change this setting to 0 (zero). Enter 999 if the total response time should be divided by the total number of images.
  • Redirection
    • Auto Redirect:
      • If True, all HTTP redirects: 301, 302, and 307 will be handled at a level lower than WebWatchBot normally handles redirects. Set this option to true if WebWatchBot is not properly handling individual redirects. This option overrides other redirection options.
  • Redirect on HTTP 301:
    • If True, WebWatchBot will automatically redirect to the URL specified in the header and/or content. Setting this option to TRUE (default) will cause WebWatchBot to act much like your browser does. This setting is overridden at the Watch Item level if the alarm condition to trigger/reset an alarm for an HTTP 301 is set.
  • Redirect on HTTP 302:
    • If True, WebWatchBot will automatically redirect to the URL specified in the headerwith the "Location:" attribute. In some cases, you may not want the automatic redirect to occur so that you can detect a problem such as a page hijack. This setting is overridden at the Watch Item level if the alarm condition to trigger/reset an alarm for an HTTP 302 is set.
  • Redirect on HTTP 303:
    • If True, WebWatchBot will automatically redirect to the URL specified in the headerwith the "Location:" attribute. In some cases, you may not want the automatic redirect to occur so that you can detect a problem such as a page hijack. This setting is overridden at the Watch Item level if the alarm condition to trigger/reset an alarm for an HTTP 303 is set.
  • Redirect on HTTP 307:
    • If True, WebWatchBot will automatically redirect to the URL specified in the headerwith the "Location:" attribute. In some cases, you may not want the automatic redirect to occur so that you can detect a problem such as a page hijack. This setting is overridden at the Watch Item level if the alarm condition to trigger/reset an alarm for an HTTP 307 is set.
  • Keep Connection
    • If True, WebWatchBot will attempt keep the connection alive for as long as possible. Set to False, if web pages do not behave properly with keep-alive semantics. This flag is required for Microsoft Network (MSN), Windows NT LAN Manager (NTLM), and other types of authentication.
  • Connection Retries:
    • The number of times that a connection to a webserver should be retried after the first connection failure. The default value is 1.
  • Timeouts
    • Send Timeout:
      • Number in millseconds to timeout the sending of an HTTP request data. Default value is 30000 (30 seconds). This is a global setting that is overridden at the Watch Item level by the alarm condition "Response Time Maximum in ms".
  • Receive Timeout:
    • Number in millseconds to timeout the receiving of an HTTP response data. Default value is 30000 (30 seconds) This is a global setting that is overridden at the Watch Item level by the alarm condition "Response Time Maximum in ms".
  • Ping
    • Destination Unreachable:
      • If Ping returns "Destination Unreachable" set to specified response time (in ms). If destination is unreachable, the response time is normally set to 0. This can skew reporting and averages, unintentionally making the Watch Item appear to respond quickly. Set to a higher number to better reflect a failure or slow response time.
  • Trace Route
    • Resolve Host Names:
      • Resolve Ip Address to hostname for each hop. Default value is False. Please note that the trace takes longer due to name resolution if this property is set to True.