Skip to content

Add a site

A site is a client's location or grouping: the head office, a branch, a data-center rack, or a logical bundle like "cloud services". Sites sit between clients and monitors — a client has sites (Add your first client), and monitors attach to sites. That's how UpAll knows which client a monitor belongs to, and how everything the client sees gets grouped.

Create a site

Open the client in the console and add a Site. Two decisions:

  • Name — think in terms your client recognizes: "Riyadh HQ", "Jeddah branch", "AWS production". The portal and status pages group monitors under these names, so name for the reader, not for yourself.
  • Timezone — defaults to Asia/Riyadh. Leave it for anything in Saudi Arabia; change it when the location genuinely lives elsewhere.

The site's place in the timezone chain

When UpAll needs a timezone for a monitor — above all to decide which calendar day each check belongs to in daily figures and report tables — it resolves one in order:

  1. the site timezone, if the monitor has a site;
  2. otherwise the workspace timezone;
  3. otherwise the platform default.

A monitor on a Dubai site therefore buckets its days by Dubai's calendar even if your workspace runs on Riyadh time — so "Tuesday's uptime" means Tuesday there. Clock times people read on incidents and alerts follow the workspace timezone instead. The full picture: Site and workspace timezones.

Why monitors should attach to sites

Attaching a monitor to a site is optional — but a monitor without one is internal: it never appears in any client's portal, in their reports, or anywhere else the client looks. That's exactly right for your own infrastructure, the systems no customer should ever see. For anything you monitor on a client's behalf, attach it to one of their sites, because the site link is what unlocks:

  • the client's portal, where monitors are listed under their sites — Client portal overview;
  • their monthly SLA reports, built from the client's monitored systems — Monthly SLA reports;
  • status pages, which render grouped by site;
  • filtering the live status wall by client.

The habit that saves rework: create the client, then its sites, then the monitors — in that order — so nothing lands internal by accident. Next: Add your first monitor.