Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Storage alerts escalation and recovery. Configure 75% and 90% alerts, monitor their delivery, acknowledge an incident and verify recovery. Current availability: Implemented; verification required.

Before you start. An authorized administrator with mandatory MFA completed. The correct company and provider permissions; keep credentials out of screenshots and chat.

Step 1. In /admin/storage open Alert settings. Review the stale-data interval and enable owner email delivery. Recipients are active TLS platform owners from the staff directory; customer administrators are excluded.

Step 2. Verify a real measured component and actual allocation. Use a separate synthetic component for acceptance, never a customer quota. Do not upload credentials in screenshots.

Step 3. Record a fresh 75% observation through a scoped collector. Confirm one warning and one owner notification. Repeat the reading to confirm deduplication.

Step 4. Acknowledge the warning, then record 90%. Confirm the critical escalation reopens the alert and creates a new notification. Acknowledgment does not disable monitoring.

Step 5. Record a fresh reading below the warning threshold. Confirm recovery and retained history. A missing or stale reading must not resolve the incident.

Step 6. Open Delivery history. Queued, accepted, uncertain, failed and suppressed are distinct. Confirm receipt in the approved owner inbox. An uncertain send needs mailbox review before retrying.

Step 7. Inspect the hosting scheduler result and the independent monitoring provider. This application cannot prove availability while its own hosting is unavailable.

Now verify the result. Warning, critical and recovered transitions occur once each. Only current TLS owners receive queued emails and portal notifications. Disabled or departed owners are suppressed before sending.

If you get stuck. A provider-accepted email is not inbox-delivery proof. If the cron has no recent completed result, investigate hosting scheduling and runtime logs. Record production email acceptance with an explicitly approved owner recipient.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.