Skip to content

Add your first monitor

A monitor is one thing UpAll checks on a schedule: a website URL, a server's IP, a device's TCP port. This guide creates your first one.

Before you start

You'll need a workspace (see Create your workspace). Attaching the monitor to a client's site is optional but recommended — monitors without a site are treated as internal and won't appear in that client's portal or reports. To set one up first, see Add a client and Add a site.

Steps

  1. In the console, open Monitors and choose Create.
  2. Site — pick the client site this monitor belongs to, or leave it empty for an internal monitor.
  3. Name (Arabic) — required; this is how the monitor appears in Arabic reports and portals. Add the English name too if your clients read English.
  4. Type — classify what you're watching: server, network device, internet link, backup, or other. This is a label for organizing; it doesn't change how the check works.
  5. Check type — how UpAll probes the target:
    • HTTP — requests a URL; anything below status 400 counts as up. Best for websites and web applications. See HTTP monitors.
    • Ping — sends ICMP echo to a host. Best for servers and network gear. See Ping monitors.
    • TCP port — opens a connection to a specific port (a Port field appears, 1–65535). Best for services like mail, databases, or RDP. See TCP port monitors.
  6. Target — the URL, hostname, or IP address to check. The field unlocks once a check type is chosen.
  7. Press Test connection to probe the target right now, before saving. You'll see success and the response time, or the exact error. See Test connection.
  8. Check every — 1 to 5 minutes; every minute is the default and the right choice for anything client-facing.
  9. Failures before incident — how many consecutive failed checks open an incident. The default of 3 balances speed against false alarms; see Check intervals and thresholds.
  10. Service class — pick what this monitor watches (a website, a REST API, an in-region TCP service, …) and UpAll fills in a sensible Degraded threshold (ms) for you; choose Custom to set your own number, or Off to skip latency tracking for this monitor entirely.
  11. Degraded threshold (ms) — responses slower than this mark the check as degraded without opening an incident. The Service class picker fills it in per check type (HTTP starts at 2000 ms, TCP port at 500 ms, Ping at 100 ms); pick Custom above to edit it directly.
  12. Leave Enabled on and save.

What happens next

The first check runs within a minute. The monitor page starts filling with the uptime timeline and latency chart (reading monitor charts), and if the target fails enough consecutive checks, an incident opens and your team is emailed — no extra configuration needed (how incidents open and close).

If you hit your plan's monitor limit, the Create button tells you; see Plans and limits.