Servers with observed issues
Terminal Guardian
Know what needs
your attention.
Evidence first. Clear next steps. Your infrastructure stays under your control.
Missing, stale or incomplete evidence
Servers with an enrolled collector
Sample timestamp: 2026-10-16T12:00:00Z · Freshness limit: 180s
Primary strategy VPS
Last observation: 2026-10-16T12:00:00Z
EA heartbeat is stale · primary-mt5
Expected EA heartbeat is 164 seconds old; limit is 120 seconds.
Next step: Inspect EA state and existing orders before considering recovery.
Observation history
Historical assessments describe that observation, not current health. Latest 20 reports for the active enrollment.
Frozen sample · no customer history is loaded.
Optional AI explanation · advisory only
AI is disabled or not configured. No request will be sent. Jev remains separately gated; the initial synthetic screen did not establish a savings benefit.
Secondary strategy VPS
Last observation: 2026-10-16T12:00:00Z
No issues found in the supplied signals. This does not guarantee trade execution or future availability.
Observation history
Historical assessments describe that observation, not current health. Latest 20 reports for the active enrollment.
Frozen sample · no customer history is loaded.
Optional AI explanation · advisory only
AI is disabled or not configured. No request will be sent. Jev remains separately gated; the initial synthetic screen did not establish a savings benefit.
New trading VPS
Last observation: Not received
No fresh observation is available. Previous readings are not shown as current.
Next step: Check collector delivery and time synchronization.
Observation history
Historical assessments describe that observation, not current health. Latest 20 reports for the active enrollment.
Frozen sample · no customer history is loaded.
Optional AI explanation · advisory only
AI is disabled or not configured. No request will be sent. Jev remains separately gated; the initial synthetic screen did not establish a savings benefit.
Resource review VPS
Last observation: 2026-10-16T12:00:00Z
High CPU usage
CPU usage is 96%; the warning threshold is 90%.
Next step: Inspect sustained usage before changing capacity or stopping any process.
Rule-based next steps
One resource or clock warning was observed. Review the recorded evidence and its manual check before considering changes.
- Inspect sustained resource usage before changing capacity.
One observation does not establish a cause or sustained load. This is deterministic guidance, not an AI diagnosis.
0 provider requests · $0 AI allowance reserved · No action executedObservation history
Historical assessments describe that observation, not current health. Latest 20 reports for the active enrollment.
Frozen sample · no customer history is loaded.
Local guidance is shown above. No paid explanation is requested for this policy’s scope.
One layer at a time.
The read-only collector reports resources and terminal-process presence. Broker connection, quotes and EA heartbeats require a terminal-side bridge; a running process does not prove these are healthy.
One known resource/clock warning or only missing signals can use deterministic guidance: no model call, no AI allowance reservation. Mixed and critical findings never use that shortcut. Optional provider explanations share the app’s persistent $10/month allowance gate; it does not control other applications or verify invoices. Jev stays off: the initial synthetic screen did not avoid any OpenAI calls at the configured threshold.
← Back to product tour