Health Check — User Guide | YoBench

What the Health Check module does

The module continuously monitors the availability of your websites and APIs over HTTP. No need to keep an UptimeRobot tab open or pay for an external monitoring service — YoBench polls the URLs you configure at a set interval, records response time, computes uptime, and sends a notification the moment a site stops responding.

Unlike the Security Scanner (which inspects configuration: SSL, headers, ports), Health Check answers a single question: "Is this site up right now?" — but it does so regularly, for years on end, and keeps history.

What you get:

• Local uptime monitoring — data lives in the encrypted database on your computer, with no third-party SaaS dependency.
• Response time — last value plus the average over the log retention window (7 days by default).
• 7-day uptime % — calculated from each check's logs.
• Notifications only on state change — when a check transitions from "up → down" or to a timeout, with no spam on every successful poll.
• Proxy and timeout support — for monitoring resources behind private networks or slow back-ends.

Monitoring parameters

When creating a check you specify:

• Name — an arbitrary label (shown in the list).
• URL — the address to poll. The module uses HTTP GET; no other methods are supported yet.
• Description (optional) — a note for yourself or your team.
• Timeout — maximum response wait time in milliseconds. Allowed range 500–60,000 ms; default 5,000.
• Proxy (optional) — pick a proxy profile from settings; all requests for this check will be routed through it.
• Enabled — activity flag. Uncheck to pause a check without deleting it.

What counts as success. A check succeeds when the HTTP response code is < 500. Anything from 200 to 499 is success. A network error becomes error. Exceeding the timeout is timeout.

Request header. All requests go out with a fixed User-Agent: AutomationsDesk/1.0 HealthCheck.

SSL. Certificates are validated normally; there is no toggle in the UI to disable SSL validation.

Global module settings

Configured under Settings → Health Check:

• Enable automatic checks — the master switch for the scheduler. Disabled by default — until you turn it on, checks only run on demand.
• Check interval (minutes) — how often the scheduler polls every enabled URL. Any value from 1 to 1440 (1 minute to 24 hours); default 5 minutes. The interval applies to the whole module; per-check intervals are not configurable.
• Log retention (days) — how long to keep history in the database. Default 7 days. The same window is used to compute uptime % and the average response time.
• Notify on timeouts — send a notification when a site stops responding within the timeout. On by default.
• Notify on errors — send a notification on a network error or a 5xx response. On by default.

Notifications fire only on state change (e.g. last result was success, current is timeout). No "all good" reminders are sent.

Notifications

Notifications go out via two channels configured in the central notification settings of the app:

• Telegram — bot token + chat ID.
• Email — SMTP (host, port, username, password, from, to, TLS toggle).

Channels are configured once for the whole of YoBench and automatically used by every module that emits notifications. Other channels (Discord, Slack, push, webhook) are not supported yet.

Workflow

1. Add a check

1. Open the Health Check module from the left sidebar.
2. Click + Add site.
3. Fill in name, URL and (optionally) description.
4. Set the timeout and pick a proxy if needed.
5. Leave Enabled ticked to start monitoring straight away.
6. Save.

2. Turn on automatic checks

1. Open Monitoring settings at the top of the Health Check page.
2. Tick Enable automatic checks.
3. Set the interval in minutes (default 5).
4. Configure log retention and notification channels.
5. Save settings.

From now on the scheduler will poll every enabled URL on that interval.

3. Run a manual check

You can run a check at any time without waiting for the next scheduler tick:

• Check next to a row — polls a single URL.
• Check all in the header — polls every enabled check in parallel.

4. Review the results

The main page shows a table with these columns:

To see the full history, click Logs next to a check. A panel opens with timestamp, status, response time, and error text per row. You can filter by status (All / Up / Down / Timeout) with pagination at 50 rows.

5. Manage checks

• Edit — change parameters (URL, timeout, proxy).
• Untick "Enabled" — pauses a check without deleting it.
• Delete (×) — removes the check and its logs (with confirmation).

Next steps

• Wire up notifications (Telegram/email) so you learn about outages immediately.
• Configure proxies if you need to monitor resources inside a private network.
• If configuration security matters as much as uptime, run the Security Scanner alongside.

Help and feedback

Found a bug or have a feature idea? Contact us via the feedback form.