Monitors
A URL with method, expected status, keyword, timeout and interval, run by a minute cron within the Workers limits.
Is everything up? Know first, tell everyone
Watch your sites and APIs, open and close incidents, plan maintenance and show a public status page with a 90-day history.
A monitor is an address with a method (GET, HEAD or POST), expected status, optional keyword present or absent, timeout, slow limit, interval of 1, 5 or 15 minutes, group and a public flag; up to 300 per domain, and unsafe addresses are refused. Checks run only from the scheduler every minute, at most 100 per run with the rest carried to the next minute; Check now queues a monitor for the next run. A host that cannot be checked from the Worker shows cannot check from here and never a false down: a connection error counts as down only for a monitor that has been reached before, a run in which all five or more of our own hosts fail counts nothing, and a real wrong answer always counts. Results are up, slow, down or cannot check, with response time, 90 days per day and uptime. An incident opens after a number of failed checks in a row and resolves after good ones (both in Settings); manual incidents carry updates; maintenance windows of up to 14 days silence alerts and stay out of uptime. Alerts are sent once per change of state by signed webhook, by email to chosen people and to confirmed subscribers. The public /status page shows monitor names only, groups, 90-day bars, incidents, maintenance, 30-day history, double opt-in email subscribe and a badge; it returns 404 until the owner turns it on. Add every APPNEURAL app of a domain imports them from the suite list as /health monitors. API /api/v1/monitors, /api/v1/incidents and a change feed with an API key or the workspace key; webhooks monitor.down, monitor.up and incident.opened, updated and resolved. Not built: Notifications as an alert channel, escalation, reminders while down, SMS, hourly graphs. Whether the scheduler can reach APPNEURAL's own hosts must be confirmed live after deploy.
What Status does for you.
A URL with method, expected status, keyword, timeout and interval, run by a minute cron within the Workers limits.
Opened after repeated failures, with manual incidents, updates and maintenance windows that silence alerts.
A public page with groups, a 90-day history, email subscribe and a badge; switchable off.
A suggested path for Status. What you can do depends on your access in the app.
Add URLs or every app of a domain.
Choose who is told.
Turn on the public page.
Live host, inventory, governance, health checks, verification, dependencies and history.
A monitor is an address with a method (GET, HEAD or POST), expected status, optional keyword present or absent, timeout, slow limit, interval of 1, 5 or 15 minutes, group and a public flag; up to 300 per domain, and unsafe addresses are refused. Checks run only from the scheduler every minute, at most 100 per run with the rest carried to the next minute; Check now queues a monitor for the next run. A host that cannot be checked from the Worker shows cannot check from here and never a false down: a connection error counts as down only for a monitor that has been reached before, a run in which all five or more of our own hosts fail counts nothing, and a real wrong answer always counts. Results are up, slow, down or cannot check, with response time, 90 days per day and uptime. An incident opens after a number of failed checks in a row and resolves after good ones (both in Settings); manual incidents carry updates; maintenance windows of up to 14 days silence alerts and stay out of uptime. Alerts are sent once per change of state by signed webhook, by email to chosen people and to confirmed subscribers. The public /status page shows monitor names only, groups, 90-day bars, incidents, maintenance, 30-day history, double opt-in email subscribe and a badge; it returns 404 until the owner turns it on. Add every APPNEURAL app of a domain imports them from the suite list as /health monitors. API /api/v1/monitors, /api/v1/incidents and a change feed with an API key or the workspace key; webhooks monitor.down, monitor.up and incident.opened, updated and resolved. Not built: Notifications as an alert channel, escalation, reminders while down, SMS, hourly graphs. Whether the scheduler can reach APPNEURAL's own hosts must be confirmed live after deploy.
Product analytics belongs to Analytics; error tracking and logs belong to the developer catalogs; the list of apps comes from the suite.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
status.appneurox.com
Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.