Server Health: Plain English Checkups and Incident Reports
Plain English checkups for your server, built only from system statistics.
The Server Health is the server health check specialist in the Ai1 platform by MyZone AI: started by the Concierge for one job at a time, it grades your Ai1 server green, amber or red from system statistics alone and writes plain English incident reports, never opening your files, projects or data.
Amber and red items arrive with the smallest sensible next step, so they can be dealt with before they turn into outages.
Clear answers after an incident
You get a plain timeline and the most likely cause, instead of a wall of logs to work through.
Your data stays private
Only system statistics and process names are collected, never your files or data, and the raw data is deleted once the report is out.
Proof that a fix helped
When the server is slow, you see the numbers from before and after each change rather than taking the improvement on trust.
Meet your agent
Get to know Siobhán
Siobhán runs health checkups and writes plain-English incident reports for your server, built only from system statistics, never your files. She is practical, reassuring and fond of her green glasses.
AI agent. Fictional persona; not a real person.
Siobhán, the persona of the Server Health
Name
Siobhán M.
Role
Server Health Specialist
Experience
29 years
Work history
Infrastructure lead at a pharmaceutical company Systems engineer at a data centre operator
Personality
Reassuring, respects privacy
Based in
Cork, Ireland
Why Siobhán has a personality
AI does better work as a specific expert, so the Server Health works as Siobhán (Server Health Specialist, Cork, Ireland). You can rename Siobhán or change the personality, experience and profile settings at any time.
You ask the Concierge, and the Concierge starts it for one job
Checkups
System, platform, containers and scheduled jobs, graded green, amber or red
Incidents
A timeline, the most likely cause and how to prevent it, for the window you give
Slow server
A CPU review with ranked fixes and before and after numbers
What it reads
System counters and log statistics only, never your files
What it changes
Nothing in checkups or incident reports
Capabilities
What the Server Health does for you
Graded health checkups
Grades the system, the platform, containers and scheduled jobs green, amber or red. For anything not green it gives the number, what healthy looks like and the smallest sensible next step.
Incident reports for a time window
For the window you name, it sets out what you experienced, the timeline, the most likely cause in plain words and what would prevent it. An honest likely beats a confident guess.
CPU usage reviews
When the server is slow or busy, it samples overall load, ranks the fixes, gets an independent review, has safe changes made by another agent and shows before and after numbers.
Flags a common cause of outages
Every report names any container running without a memory limit, the most common reason a whole server goes down.
Privacy first
It never opens, lists, reads or searches your files, folders, projects or databases, and the raw collected data is deleted once the report is published.
How the Server Health differs from a monitoring dashboard
A monitoring dashboard shows numbers and leaves you to work out what they mean. Server Health grades each area green, amber or red and, for anything not green, gives the number, what healthy looks like and the smallest sensible next step. After an incident it writes a plain timeline and likely cause, and it builds every report from system statistics alone, never from your files, projects or data.
How this differs from the Disk Health: Disk Health finds what fills the disk and clears only the items you approve, while Server Health runs checkups and incident reports from system statistics.
How it works
From your request to a finished result
It runs inside your Ai1 system and works in the tools you already use. You ask, it works, it reports, and it stops for your OK where it matters.
Tap the diagram to enlarge it
Step 1: Ask
You ask the Concierge for a checkup or about an incident, and the Concierge starts Server Health for that one job.
Step 2: Collect
Fixed collectors gather system statistics and process names, never your files or data.
Step 3: Grade
Each area is graded from the collected data and nothing else.
Step 4: Report
One report appears on the Server Health tab, including a note of exactly what was collected.
When to use it
Hand these situations to the Server Health
Illustrative photo. Asking the Concierge whether the server is healthy and what happened overnight.
If this is you…
…here's what it does
You want to know if the server is in good shape
It runs a checkup and returns a graded board with the next step for anything amber or red.
Your site was down for an hour overnight
You give the time window and get a server incident report: the timeline, the most likely cause in plain words and how to prevent it.
The server feels slow
It runs a CPU review, ranks the fixes, has the safe ones made by another agent and shows the before and after numbers.
Everything turns out to be fine
It tells you the server is healthy. That is a good report, not a missed problem.
What you get
Server diagnostics in one graded board: the system, the platform, containers and scheduled jobs
For each amber or red item: the number, what healthy looks like and the next step
Incident reports with a timeline, the likely cause and how to prevent it
CPU reviews with ranked fixes and before and after numbers
A warning for any container running without a memory limit
A note of what was collected for each report
What it won't do
✕Talk to you or choose the job and time windowHandled by: Concierge
✕Make other changes to your serverHandled by: You, through the Concierge
Example incident report
Example: Incident report for an outage
Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources.
What it was asked: Last night, right after the wine club email went out, the online shop crawled and then would not load for a while: what happened, and how do we stop it happening again?
Example report
What you experiencedTimeline of the windowLikely cause and preventionThis morning and what was collected
What it found: 3 findings, with the numbers
The shop showed error pages for 26 minutes, 21:38 to 22:04 on 30 Sep, after the server ran out of memory twice and stopped the shop's database during the wine club release.
The likely cause is the photo resizing tool, which has no memory limit and ran 8 workers using 3.4 GB of the server's 8 GB while new bottle photos were processed.
Three of the four shop containers have no memory limit. Capping them is the smallest fix; nothing was changed, because that change is the owner's call, made through the Concierge.
A sample incident report for a fictional vineyard in the agent's usual structure: what the owner experienced, the timeline of the window given, the most likely cause with an honest confidence level, what would prevent it, and what was collected. All figures are invented; no real server, files or customer data were read. Server Health changes nothing: the suggested memory limits are the owner's decision, made through the Concierge. Run date: .
Takes care of disk space, finding what fills the disk and clearing only the items you approve.
Common questions
Frequently asked questions about the Server Health
What should a server incident report tell a business owner?
What you experienced, a timeline of the window, the most likely cause in plain words and what would prevent it. Server Health in Ai1 by MyZone AI writes this from system statistics for the time window you give, and an honest likely beats a confident guess.
If you have not given a time window, it asks rather than guess.
When is a CPU usage review worth running?
When a server feels slow or stays busy. Server Health samples the server's overall load, ranks possible fixes and has them reviewed independently. Safe changes are then made by another agent, and you see the numbers from before and after each change rather than taking the improvement on trust.
Can server diagnostics run without reading business files?
Yes. Server Health's fixed collectors gather only system statistics and process names. It never opens, lists, reads or searches your files, folders, projects or databases, and the raw collected data is deleted once the report is published.
If the data cannot answer a question, it tells you the answer is not in the collected data instead of guessing. Server Health is available now on the Ai1 server it runs on.
How do I ask for a Server Health checkup, and will it change settings?
Ask the Concierge in chat. It starts Server Health for that one job and the report appears on the Server Health tab.
Checkups and incident reports alter nothing. The only changes come during a CPU review, where another agent makes them and the result is checked with before and after numbers. Anything else is your decision, through the Concierge.
About Ai1
Do I get just the Server Health, or the whole platform?
The whole platform. The Server Health is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Compare plans →
Two paths, one platform. Build it yourself on a developer plan, or let our team run your AI operations for you. Every plan runs on its own private server, and every price is shown in full. See Ai1 pricing →
Operations
Operations
Operations
Operations
Operations