A moment can cross the line. An alert waits until it stays there.
Choose a server metric, set the threshold, and decide how long the condition must continue. If that configured condition is met, FocalShift sends an email to your account address.
Four server metrics. One clear starting point.
Create a policy around CPU, memory, disk, or one-minute load. Each policy watches one selected metric for the server in your FocalShift view.
CPU selected for this illustration.
One metric per policyThe alert form selects one supported metric.
One server contextThe policy is bound to the member’s server in the current view.
Your decisionYou choose the threshold and sustained window.
A crossing begins the condition. Staying there completes it.
The current rule uses “greater than,” a whole-number threshold from 1 through 100, and one of four sustained windows. The threshold is yours—not a universal recommendation.
Threshold ready. Choose the duration.
If you cannot read it, it should not interrupt you.
Metric tells FocalShift what to evaluate. Threshold defines the line. Duration decides whether the configured condition lasted long enough. The destination is the valid email address on your account.
A quiet list should still tell the truth.
The current view can show Active or Paused policies, an honest empty state, or an unavailable list. Paused is a state the list can display; this page does not claim a pause or resume control.
The returned policy is enabled.
The returned policy is not enabled. No pause/resume action is promised here.
No policies are currently listed for the selected server. That is not the same as “all clear.”
FocalShift could not load the policy list. Unknown remains unknown.
Add a valid email address to your profile before creating an email alert.
Remove the policy—not the monitoring signal.
Deleting an owned policy requires confirmation. The policy leaves the member’s alert list and future email for that rule stops. The current view offers no undo or restore.
Bound to the server in your authenticated view.
FocalShift resolves the server within the signed-in member context, associates creation with that server, and checks ownership before deletion is allowed.
The management view requires a signed-in member.
The policy belongs to the server in the member view.
Deletion is refused when that association is not present.
The email starts the human review.
A threshold alert reports that a configured condition was met. It is not a diagnosis, an outage declaration, or an automatic repair. You decide what follows.
Server Management
Review the selected server’s operating context and available controls.
02 / UnderstandAnalytics & Insights
Look at the resource behavior around the condition without inventing a cause.
03 / PrepareBackups & Recovery
Know the available return path before a consequential change.
04 / Get help支持中心
Open documentation, the Knowledge Base, and support tickets.
Let the condition earn the email.
Create a clear threshold policy for CPU, memory, disk, or one-minute load—and keep the final decision in human hands.