Step by step explanation of the Wormly test cycle

The following example describes the monitoring of a host configured with a single HTTP Request sensor on a 2 minute interval.

Every 2 minutes, the test cycle begins.

1. The primary monitoring node assigned to your host makes an HTTP request according to the URL and other parameters you have configured.

2. The primary node considers your host to have failed if:

  • There is no response - or only a partial response - received within the specified timeout period.
  • An incorrect response is received (e.g. wrong HTTP response code, expected text missing, invalid SSL certificate, etc)

3. If the primary node deems the host to have failed, it communicates with 4 other Wormly monitoring nodes, instructing them to conduct the same test from their location.

4. If any Wormly node disputes the failure (i.e. considers the host to have passed the test) then the failure is considered a false positive, and consequently ignored.

5. If all Wormly nodes confirm the failure, then the failure is recorded in the logs and any configured alerts are sent.

Test cycle ends.
Logs are propagated from monitoring nodes onto data processing servers for aggregation and reporting.

Each test has a maximum 60 second timeout period. While the primary monitoring node will wait for up to 60 seconds before failing with a timeout condition, confirmation nodes will wait only 8 seconds to confirm a failure. This is a compromise designed to speed up the transmission of alerts.

For hosts with multiple sensors, each sensor is checked sequentially. The failure of any sensor will trigger a failure for the entire host.

Not what you were looking for? Try a search:

Ninja Tip: trace* will match traceroute.

Also in this topic: