Alerts
Alerts identify warning and critical conditions that MyOwnProxy currently detects for Gateways and Nodes. Open Observability and select Alerts.
Alerts are read-only and are recomputed from current resource state, health information, and heartbeats. They are not retained incidents or tickets. When a condition no longer applies, its alert disappears on a later refresh rather than moving into alert history.
Severity and coverage
The current severity levels are:
| Severity | Customer meaning |
|---|---|
| Critical | A Gateway or Node is OFFLINE, or a reported resource measurement is in its critical range. Review service impact immediately. |
| Warning | A resource is DEGRADED, a heartbeat is stale, a Node has no operational Gateway assignment, or a reported resource measurement is elevated. Investigate before it affects service. |
Gateway alerts cover OFFLINE or DEGRADED state, stale heartbeat, high CPU load, high memory use, and high disk use. Node alerts cover OFFLINE or DEGRADED state, missing operational Gateway assignment, stale heartbeat, and high CPU, memory, disk, or temperature readings.
Alerts do not currently cover Proxies or Pools. Use Candidate Diagnostics and the Proxy details page when investigating Pool behavior.
Filter and review alerts
You can filter the current list by:
- Severity: Critical or Warning.
- Entity Type: Gateway or Node.
- Gateway.
- Resource State.
Select Clear to remove the filters. Filtering changes only the displayed list; it does not acknowledge, dismiss, or alter an alert.
The count shown with the Alerts tab reflects the current filters. Each row shows a severity indicator, resource type and ID, title and message, current state, and related Gateway ID.
Use Health Explorer to review the Gateway or Node's current heartbeat and health information.
Respond to an alert
- Refresh Observability and confirm that the alert still appears.
- Review the severity, resource, state, message, and related Gateway.
- Open Health Explorer and check the resource's last heartbeat and current health information.
- Determine which Proxies, Pools, and applications depend on the affected resource.
- Follow Gateway Problems or Node Problems, as applicable, or contact MyOwnProxy Support if the resource does not recover.
There is no alert acknowledgment, dismissal, mute, manual clear, or direct remediation action.