ATStatus
ATStatus WikiLoading documentation...

Automatic Monitoring

ATStatus automatically monitors your services and updates their status based on real-time availability checks.

24+
Monitor Types
60s
Default Interval
3
Retry Attempts
<100ms
Response Time

How Monitoring Works

The monitoring system continuously checks your services and automatically updates their status:

MonitorHTTP, TCP, DNS...
Scheduler30s - 24h intervals
Status ChangeUp → Down detected
NotifyEmail, Discord, Webhook

Monitor Types

HTTP/HTTPS

Web endpoints & APIs

TCP Port

Services & databases

Keyword

Content validation

Database

SQL & NoSQL

Enabling Monitoring

Per-Component Monitoring

Each component can have its own monitoring configuration:

  • Navigate to Admin → Components
  • Click on a component to edit it
  • Enable Automatic Monitoring
  • Set Monitor URL, Type, and Interval
  • Click Save

Global Monitoring Settings

Configure system-wide settings in Admin → Settings → Monitoring:

SettingDescriptionDefault
Default IntervalDefault check interval for new components60 seconds
Default TimeoutRequest timeout before marking as down30 seconds
Retry CountNumber of retries before marking as down3
Status ThresholdsResponse time thresholds for degraded status1000ms / 3000ms

Status Calculation

Component status is automatically calculated based on monitoring results:

Successful response, fastOperational
Successful response, slowDegraded
Failed after retries, some successPartial Outage
All checks failedMajor Outage
During maintenance windowUnder Maintenance

Running the Monitor

Manual Execution

Run monitoring checks manually:

npm run monitor

Automated via Cron

Set up automated monitoring with cron:

# Using curl (every minute in crontab)
* * * * * curl -X POST https://your-status-page.com/api/cron/monitor -H "Authorization: Bearer YOUR_CRON_SECRET"

# Or using the monitor daemon
npm run monitor

Security Note

Protect the monitor endpoint with your CRON_SECRET environment variable. This prevents unauthorized users from triggering status updates.

Uptime Metrics

ATStatus tracks and displays uptime metrics for each monitored component:

Uptime Percentage

Calculated from monitoring data (e.g., 99.95%)

Response Time

Average latency in milliseconds

Uptime Chart

Visual history of availability (90-day default)

Troubleshooting

Monitor Not Running

  • • Verify CRON_SECRET is set in your .env
  • • Check that the cron job is configured correctly
  • • Review server logs for errors

False Positives/Negatives

  • • Increase timeout for slow services
  • • Increase retry count for flaky connections
  • • Verify the monitor URL is correct
  • • Check network/firewall settings

Manual Override

You can manually override the component status at any time. When you manually set a status, automatic monitoring will resume on the next check unless you disable monitoring.