Create first LAN monitor

In short: After installing the agent you create a LAN monitor via the "Add new monitor" button. In the type dropdown choose lan_ping, lan_tcp or lan_http, fill in the target and select the agent from the list.

Step by step

1. In the dashboard click + Add new monitor.
2. Enter a name (e.g. "NAS Synology - backups" or "Reception printer").
3. In the Monitor type field choose one of the LAN types - see the table below.
4. In the URL/hostname/host:port field enter the target.
5. In the LAN agent field select the agent that should perform the check.
6. Set the Interval (minimum depends on the plan).
7. Press Create monitor.

Types and target format

Sub-millisecond measurements

For LAN targets the RTT is typically less than 1 millisecond (e.g. 0.05 ms on local ethernet). ePulz.io stores response_ms as a float with precision to 3 decimal places. In charts and the dashboard you see exact values instead of rounding to whole milliseconds.

What happens during the first check

1. The monitor is saved with last_status = pending.
2. The agent at the next pull cycle (within 30 s) receives the task.
3. It performs a local ping/TCP/HTTP check.
4. Sends the result back via HTTPS. In the dashboard you will see up or down with response time.

Troubleshooting

• The monitor stays in the "pending" state - check that the agent is running (journalctl -u epulzio-agent -f or docker logs epulzio-agent).
• ping returns DOWN from the agent, but ping from the host works - in the Docker variant --network host is missing; the container is in an isolated network.
• lan_http returns DOWN with an SSL error - the target has a self-signed cert. Use http:// instead of https:// for internal web applications.
• I am getting a lot of false-positive alerts - increase notify_after_failures in the monitor detail (e.g. 3 = alert only after 3 consecutive failures).