Guides
Knowledge base
How uptime and latency monitoring works, and how to use every part of UpAll — from your first monitor to monthly SLA reports.
Monitoring concepts
What is uptime monitoring?
What uptime monitoring measures, how automated checks work, and why IT service providers treat it as core infrastructure.
What is downtime?
What counts as downtime, the failures that cause it most often, planned versus unplanned outages, and what an hour of downtime really costs a small business.
The nines of availability
What 99%, 99.9%, and 99.99% availability allow in real downtime per month and year, what each extra nine costs, and which target actually fits an MSP client.
What is latency?
Latency is the time between request and answer. What the millisecond numbers mean, what users notice, and why an up-but-slow system is still a problem.
Latency vs bandwidth
Bandwidth is how wide the pipe is; latency is how long a round trip takes. Why more bandwidth doesn't make things faster, and which one monitoring measures.
Percentiles and p95, explained
Why average response times hide real problems, what p50, p95, and p99 mean, and why UpAll reports the 95th percentile on status pages and in reports.
What is an SLA?
What a service level agreement commits you to, how uptime targets and measurement windows work, and why an SLA needs continuous independent measurement.
SLA, SLO, and SLI
SLI, SLO, and SLA are three different tools: the measurement, the internal objective, and the external promise. How they fit together in day-to-day MSP work.
How HTTP checks work
What happens inside an HTTP check step by step, how status codes decide up or down, and UpAll's exact rules for redirects, timeouts, and content.
How ping checks work
What an ICMP echo probe actually tests, why a reachable host is not the same as a working service, and when ping is the right check type.
How TCP checks work
How a TCP check completes a handshake on a specific port to prove a service is listening, what that evidence leaves out, and common ports.
DNS and monitoring
How name resolution works, the ways DNS itself takes services down, and how a failed lookup shows up in your HTTP and ping check results.
SSL/TLS certificates explained
What a TLS certificate proves, how the chain of trust works, validity windows and 90-day automated renewals, and what browsers do when it breaks.
Certificate expiry risks
What actually breaks the moment a TLS certificate expires, why capable teams still miss renewals, and how a 30-day warning closes the gap.
Incidents and severity
What an incident is, why severity ladders like Info, Degraded, and Outage exist, and the lifecycle every incident follows from open to resolved.
False positives and flapping
Why one failed check is weak evidence of an outage, how consecutive-failure thresholds filter the noise, and how they calm flapping monitors.
Monitoring intervals
The trade-off behind check frequency — what 1-minute and 5-minute intervals can each detect, and the math that sets your time to alert.
Why MSPs monitor
The business case for monitoring as an MSP — finding problems before the client does, proving SLA compliance, and turning uptime into retention.
Getting started
Create your workspace
How to sign up for UpAll — choose a company name and subdomain, create the admin account, and find your console. Starts free, no card required.
Workspace settings and branding
The admin-only workspace settings in UpAll — logo, company name, contact email, VAT number, brand color, and what the workspace timezone controls.
Add your first client
What a client is in UpAll, how to create one with its logo, report language and SLA target, and how the limit on clients behaves.
Add a site
What a site is in UpAll, how the site timezone fits the site → workspace → default chain, and why monitors should be attached to sites.
Add your first monitor
Step-by-step guide to creating a monitor in UpAll — choosing a check type, setting the target, and tuning the interval and thresholds.
Invite your team
Admin and Engineer roles in UpAll, adding staff directly or with invite links, deactivating accounts, and how the last-admin protection works.
Switch language and theme
Switching the UpAll interface between Arabic and English per user, how the choice persists, dark mode in the console, and KB language URLs.
Monitors
Monitor types and check types
How a monitor's type label differs from its check type in UpAll, and how to pick the right probe — Ping, HTTP, or TCP — for each target.
HTTP monitors
How HTTP monitors work in UpAll — the under-400 success rule, redirect handling, the fixed 10-second timeout, and automatic certificate watching.
Ping monitors
How Ping monitors check servers and network devices with ICMP, what reachability proves, and what to do when firewalls block ICMP traffic.
TCP port monitors
How TCP port monitors verify that a specific service is accepting connections — mail, databases, RDP — and what a successful connect proves.
Check intervals and thresholds
How the check interval and failures-before-incident settings decide detection time, with worked examples and tuning advice per criticality.
The degraded latency threshold
What the Degraded status means in UpAll, how the latency threshold works, its per-type maximums, and how to disable latency as a health signal.
Test connection
What the Test connection button does in UpAll — an immediate probe before saving, what it returns, its rate limit, and which targets it refuses.
Pausing monitors
How the Enabled toggle pauses a monitor in UpAll, what stops and what is kept, and how to use pausing during planned maintenance work.
Monitor statuses explained
What Up, Down, Degraded, Paused, and Unknown mean in UpAll, the exact conditions that trigger each status, and where the colors appear.
Reading monitor charts
A tour of the monitor page in UpAll — the time-window selector, summary tiles, uptime timeline, latency chart, and how retention shapes long views.
SSL certificate monitoring
How UpAll automatically watches TLS certificates on HTTPS monitors, the incidents it opens as expiry approaches, and where the warnings appear.
Site and workspace timezones
How UpAll resolves a monitor's timezone from site to workspace to default, what each zone controls, and why storage stays in UTC underneath.
Incidents & alerts
How incidents open and close
How UpAll opens an incident after consecutive failed checks, backdates the start to the first failure, auto-resolves on the next OK check, and emails your team.
Incident severities
What Info, Degraded, and Outage mean in UpAll, which incident sources produce each severity, and how to choose the right one for a manual incident.
Manual incidents
When to record an incident by hand in UpAll, what every field controls — including whether the client sees it — and how one-click Resolve works.
Certificate incidents
How UpAll turns TLS certificate trouble on HTTPS monitors into a two-stage incident ladder, why cert incidents stay internal, and one honest caveat.
Email alerts
Who gets emailed when an incident opens or resolves in UpAll, what the message contains, and the honest limits of alerting today — email only.
Stale monitors and the Unknown state
Why a monitor turns grey when fresh results stop arriving, what staleness usually means, and how UpAll tells your team once per episode.
The live status wall
Using the console Status page as your NOC view — every monitor ranked worst-first, a client filter, uptime bars, 24-hour latency, and the SSL strip.
Status pages & client portal
Public status pages
What a public status page is in UpAll, how to create and publish one, and how the token link, site grouping, and overall banner work.
Status page options
The four content toggles on an UpAll status page — uptime, response times, 90-day history, and recent events — and when to enable each one.
Sharing and regenerating links
How a status page URL works as the only key, who to share it with, and how Regenerate link revokes the old URL the moment you press it.
Client portal overview
What a client sees after signing in to the UpAll portal — branding, live status, month uptime, 90-day history, and their last 10 incidents.
Inviting client users
How to give a client's staff portal access with an invite link — seven-day validity, an optional email lock, and Google-only redemption.
Google access requests
What happens when someone signs in to the portal with Google but has no account — the pending queue, approving them to a client, or rejecting.
Previewing a client portal
How staff open any client's portal exactly as that client sees it — the same live page, marked as a preview — before inviting users or during a call.
Reports
Monthly SLA reports
How UpAll generates a monthly PDF SLA report for each client, when the run happens, and where the finished files land.
What's in a report
A section-by-section tour of an UpAll monthly SLA report — the summary numbers, the per-system table, the incident log, and what coverage means.
Report language and timezone
Why a report renders in the client's language rather than yours, which timezone defines each day's numbers, and which clock stamps the times.
Downloading reports
Where finished SLA reports live in the console, how to read the archive's badges, coverage and status columns, and how reports reach your clients.
Billing & account
Plans and limits
How UpAll's limits work — what they apply to, when they're enforced, what happens when you reach one, and where to see the current numbers.
Upgrade and plan changes
How admins subscribe or switch plans from the Billing page — the card checkout, scheduled changes at the next renewal, and cancelling auto-renew.
Payments, invoices and VAT
How UpAll charges your card, what VAT-inclusive pricing means in riyals, and how simplified Saudi tax invoices with ZATCA-style QR codes reach you.
Renewals and grace
What happens on your renewal date, the retry schedule when a card charge fails, the ten-day grace period, and what the downgrade at the end of it actually means.
Workspaces and multiple accounts
How workspaces isolate each MSP's data, why an account belongs to exactly one workspace, and how the same email works across several of them.