Hund offers a free-of-charge native monitoring solution to track your services without the need of a third party.
This watchdog will report the status of any given ICMP, HTTP, or DNS target. If there is a protocol you wish to see support for, let us know at firstname.lastname@example.org!
The method to use to check the target.
The host the check will make calls to.
In the case of DNS, this is the domain/IP address that will be queried. IP addresses do not need to be converted to the
z.y.x.w.in-addr.arpa format, as this will be done automatically. Of course, we accept both formats for DNS.
The regions you would like the target to be checked from. All regions are weighted equally when calculating the outcome of a check. There are no limits or extra costs for using multiple regions.
The frequency of the check in milliseconds. The minimum frequency is 30 seconds. Any frequency less than 60 seconds will force the component to become High-Frequency, at an additional cost. For specific pricing information, please visit the pricing page.
The maximum number of milliseconds the check should wait on the host before failing.
In the case of DNS, the timeout is only used as the maximum wait time for SOA queries.
Percentage Regions Failed Threshold
The percentage of regions that must report a failed check before the entire check can be considered failed.
Note: this is a number between 0 and 1.
Consecutive Check Threshold
The number of consecutive check pairs that must fail to report an outage on the component. A value of 0 will report outages upon the first check failure. A value n greater than 0 will report an outage once n+1 checks fail in a row.
Degraded on Failure
Report this component as degraded (rather than operational) on the first failures before the consecutive check threshold is satisfied.
ICMP (ping) Options
Percentage Failed Threshold
The percentage of addresses at the given target that must fail for a region to be counted as failed. This option only matters when there are multiple IP addresses behind the target when the target is a domain.
Note: this is a number between 0 and 1.
The IP version to use when pinging.
An optional HTTP Basic Authentication username.
An optional HTTP Basic Authentication password.
Response Body Must Contain...
If the requested page does not contain this exact string, then the check will fail.
Response Code Must Be...
If the requested page does not return this response code, then the check will fail.
Follow any HTTP redirects given by the requested target. Please note that this check will only follow up to 9 redirects.
Verify Target TLS Certificate
Require the target's TLS certificate to be valid.
The type of DNS record to query for on the target. Currently, we support the A, AAAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT record types.
An optional list of nameservers to make DNS queries with. This field is ignored by SOA queries since they use the nameservers yielded by querying NS on the target.
Responses Must Contain...
A list of assertions to make against the records yielded by the query. The format of these assertions is similar to DNS record syntax, but is slightly simplified and allows for only asserting parts of a record's RDATA, rather than the entire thing. The check will fail depending on the value of Response Containment.
This field is ignored by the SOA check, as it does not use assertions to determine the validity of SOA records. Instead, we ensure that every nameserver reported by querying NS on the target reports the same SOA serial. If your target's nameservers report conflicting SOA serials, we consider the check failed.
Example Assertions (for MX record type):
Note above how we can assert both the priority and domain (without the terminating period required by canonical DNS) of an MX record, or instead simply the domain.
Whether all of the assertions in the given list must match the DNS response, or rather just any of them (i.e. at least one).
Components of any kind can display the following metric(s). If you're using a different component type, just click the Add Metric Source button on the component's dashboard page.
ICMP (ping) Metrics
This is the response time from your check's target to our servers.
The total number of addresses pointed to by the given target.
The number of addresses from the total that responded to the ICMP ping.
The amount of time it took from the start of the first connection through all redirects to just before the connection to the destination host is made.
DNS Lookup Time
The amount of time it took to resolve the DNS name of the destination host.
TCP Connection Time
The amount of time it took to establish a TCP connection with the destination host after resolving DNS.
TLS Handshake Time
The amount of time it took to perform the TLS handshake (if applicable) after the TCP connection was established.
Content Generation Time
The amount of time it took for the destination host to generate the content sent to the caller.
Content Transfer Time
The amount of time it took for the content to be transferred to the caller after it was generated.
Total Elapsed Time
The total amount of time it took for the HTTP request to finish, including all redirects.
Time to First Byte
The total amount of time, including all redirects, it took for the destination host to send the first byte of its generated content to the caller.
The DNS check does not currently report any metrics.