#CES Stat — Status Page Guide

CES Stat is our status page — the public page where visitors can check
whether our services are up, and the staff panel where we manage that
page day to day. This guide is for anyone who needs to use the staff
panel; it doesn't require any coding knowledge.

If you're looking for installation/server setup instructions instead,
see the project's README.md — that's written for whoever hosts the app.

#Logging In

Go to /login.php on the status page's domain.
Enter your staff email and password.
You'll land on the Home tab, which shows a live preview of exactly
what visitors see on the public page.

If you don't have a staff login yet, ask whoever administers the site to
create one for you.

#Getting Around the Staff Panel

Across the top of every staff page you'll see five tabs:

Home — live preview of the public status page
Categories — groups that services are organized under (e.g. "Websites," "Databases")
Services — the individual things being monitored (a website, an API, a server)
Incidents — open and past outage/maintenance reports
Site Settings — the page's name, color, description, and alert contacts

Two shortcut buttons — Create Service and Create Incident — sit
just below the tabs on every staff page, since those are the two things
you'll do most often.

#Managing Services

A "service" is anything you want visitors to see a status for — a
website, an API, a login server, etc.

To add one: go to Services → Create Service, then fill in:

Field	What it means
Position	Controls the order services are listed in — lower numbers show first. Leave gaps (10, 20, 30) so you can slot new ones in between later.
Name	What visitors see, e.g. "Main Website"
Category	Which group it's listed under (or "No Category" to list it on its own)
IP / Domain	What CES Stat checks to see if it's online
Port	Only needed if you're checking a specific port; leave blank for a normal website check
History Creation	Enabled shows a 90-day uptime bar for this service; Disabled just shows its current status with no history
Tip	An optional short note that appears as a "?" hint next to the service name

To edit or remove one: go to Services, find it in the list, and
use the Edit or Delete link on the right. Deleting a service also
deletes its uptime history — that can't be undone.

#Managing Categories

Categories are just a way to group related services together on the
public page (they show up as a collapsible section). Go to
Categories to add, rename, or delete one. Position works the same
way as it does for services — lower numbers appear first.

#Handling an Incident

Use incidents to tell visitors about an outage or planned maintenance in
real time.

Opening a new incident:

Click Create Incident.
Give it a clear title (e.g. "Website Slow to Load").
Choose an impact level — Minor, Major, Critical, or
Maintenance. This also automatically updates the status shown for
any services you check off below.
Write your first message — this is what visitors see first on the
incident's page.
Check off which services are affected, then submit.

Posting an update: go to Incidents, find your open incident, and
click Update. Add a new message any time something changes (e.g. "we
found the cause and are deploying a fix").

Resolving it: on that same Update page, write your final message and
check Mark resolved & close this incident. This automatically:

Marks the incident closed
Moves the affected services back to "Operational"
Notifies subscribers and alert contacts that it's resolved

You can also close an incident instantly from the Incidents list
using the Close link, without a custom final message.

#Site Settings

Under Site Settings you can update:

Site name, color, and description — shown at the top of the public page
Allow Subscriptions — turns the public "Subscribe For Updates" button on or off
Discord Webhook Link — paste a Discord webhook URL here to have incident/outage alerts posted into a Discord channel
Service Alerts — add phone numbers or email addresses here to have staff notified directly (by SMS or email) whenever a service's status changes or an incident is posted

#What Visitors See

Visitors never see the staff panel — they only see:

The public status page (/index.php), with the overall status banner, each service's status and uptime bar, and a list of past incidents
Individual incident pages, showing the full timeline of updates
A Subscribe For Updates form (if subscriptions are enabled), where they can enter their email to get notified on future incidents

#Getting Help

If something looks wrong on the public page and you're not sure why —
for example, a service's uptime bar hasn't updated in a while, or alerts
aren't going out — that's usually a server-side/technical issue (the
automatic checker not running, or email/SMS/Discord not configured)
rather than something fixable from the staff panel. Pass those along to
whoever manages the server, referencing this guide's companion
README.md, which covers that side of things.

CES Stats