Settings
Manage your account, alerting, and integrations.
Account
Your login details and session information.
Signed in as
—
Monitoring Defaults
Default settings applied to new monitors.
Default check interval
How often new monitors check by default.
Alert after consecutive failures
Ignore flaps — only alert after N failures in a row.
Default User-Agent
Browser identity sent with every monitor request. Helps avoid bot-detection blocks.
Alert Channels
Configure email, Slack, PagerDuty, webhooks, and more.
Active channels
View all →External Scheduler
Checking…Runs your monitors 24/7 — even when no browser is open.
Beacon's monitors need a scheduler to run checks on a timed interval. Set up a free external cron at cron-job.org to keep your monitors running around the clock.
- 1 Create a free account at cron-job.org
- 2 Create a new cron job with the URL below, method POST, interval every 1 minute
- 3 Save and enable — your monitors will run 24/7 from that point on
Last scheduler run
Loading…
Checks run today
—
Total checks
—
AWS CloudWatch
Monitor EC2 CPU, network, disk and status metrics.
Connect one or more AWS accounts and select which EC2 metrics to pull into Beacon on a 5-minute polling cycle. Metrics appear alongside your existing monitors.
- ▸ CPU Utilization
- ▸ Network In / Out
- ▸ Network Packets
- ▸ Status Checks
- ▸ Disk I/O (EBS)
- ▸ EBS Throughput & Latency
- ▸ Auto Scaling Metrics
Each AWS account needs its own Access Key ID + Secret Access Key (read-only IAM is sufficient).
Manage AWSComing soon
More integrations are on the roadmap.