Skip to content

Add a service

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

Create a service

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

  • Name — think in terms your client recognizes: "Riyadh HQ", "Jeddah branch", "AWS production". The portal and status pages group components 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 service's place in the timezone chain

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

  1. the service timezone, if the component has a service;
  2. otherwise the workspace timezone;
  3. otherwise the platform default.

A component on a Dubai service 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: Service and workspace timezones.

Why components should attach to services

Attaching a component to a service is optional — but a component 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 services, because the service link is what unlocks:

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

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