Sentinel
Sentinels in Abyss Monitor probe your endpoints at a regular interval to measure availability and latency. Each Sentinel is attached to an Application and runs continuously, independently of application logs or events.
Sentinel types
Three types cover common needs:
PING
Sends an ICMP ping to a host (host). Ideal to check that a machine or network device responds.
HTTP
Performs an HTTP request (GET, POST, etc.) against a URL. You can configure:
- the headers to send,
- SSL verification (enabled by default, with an option to allow self-signed certificates),
- accepted response status codes,
- a body assertion (
containsor regex).
TCP
Opens a TCP connection to a host:port. Useful to monitor a database, a broker, or any internal service without HTTP.
Success policy
Each Sentinel defines an acceptable latency range (min, max in milliseconds). A check is treated as success if:
- the request succeeds according to the type's rules (ping received, expected HTTP status, TCP connection opened),
- latency is within the range,
- the optional body assertion passes.
Otherwise the check is a failure. A retry policy (up to 5 attempts) avoids false positives on transient drops.
Create a Sentinel
- Open the relevant Application in Abyss Monitor.
- Go to the Sentinels tab and click Create.
- Pick the type (PING, HTTP, TCP) and fill in the target.
- Set the acceptable latency range and, for HTTP, the headers and assertion rules.
- Confirm: the Sentinel starts immediately.
Visualize Sentinels
The Sentinels list shows for each one:
- the current status (success / failure),
- the recent average latency,
- the date of the last check.
Click a Sentinel to see the check history: every check is kept along with its latency, status, metadata (HTTP code, SSL info, etc.) and any error message.
Alerts and webhooks
A Sentinel can trigger: