Measuring Script Run Time

Append /start to a ping URL and use it to signal when a job starts. After receiving a start signal, will show the check as "Started." It will store the "start" events and display the job execution times. Aryas-HealthChecks calculates the job execution times as the time gaps between adjacent "start" and "success" events.

Alerting Logic

Aryas-HealthChecks applies an additional alerting rule for jobs that use the /start signal.

If a job sends a "start" signal, but then does not send a "success" signal within its configured grace time, Aryas-HealthChecks will assume the job has failed. It will mark the job as "down" and send out alerts.

Usage Example

Below is a code example in Python:

import requests
URL = ""

# "/start" kicks off a timer: if the job takes longer than
# the configured grace time, the check will be marked as "down"
    requests.get(URL + "/start", timeout=5)
except requests.exceptions.RequestException:
    # If the network request fails for any reason, we don't want
    # it to prevent the main job from running

# TODO: run the job here
fib = lambda n: n if n < 2 else fib(n - 1) + fib(n - 2)
print("F(42) = %d" % fib(42))

# Signal success:

Viewing Measured Run Times

When Aryas-HealthChecks receives a "start" signal followed by a regular ping or a "fail" signal, and the two events are less than 72 hours apart, you will see the time delta displayed in the list of checks. If the two events are more than 72 hours apart, they are assumed to be unrelated, and the time delta is not displayed.

List of checks with durations

You can also see durations of the previous runs when viewing an individual check:

Log of received pings with durations