DevOps
Monitor Netlify with MrCron
MrCron mirrors Netlify site deploy counts, ready/building/error state, and per-site failed deploys every 5 minutes so you can watch your frontend fleet in one place.
How MrCron monitors Netlify
- Total sites plus ready, building, and error counts across your Netlify account.
- Per-site failed-deploy alerts routed through your notification channels.
- Workspace-wide roll-up: connect one API token, auto-link every Netlify site.
- Per-project override: attach a specific Netlify site to a specific MrCron project.
- Auth-failure detection with an amber Rotate key CTA when the API token stops working.
What you will see
Sites total, ready, building, error counts + per-site failed-deploy alerts.
Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Netlify
Sign in, create a project, and connect Netlify in under a minute. First check ships in the free tier.
Frequently asked questions
- What Netlify credentials does MrCron need?
- A personal access token from the Netlify user settings page. MrCron stores it encrypted at rest and only decrypts it inside the sync worker.
- How does auto-linking work for Netlify?
- After you connect a Netlify account, MrCron lists every site on the account and lets you choose auto-link, manual link, or ignore per site.
- Does MrCron read Netlify build logs?
- No. MrCron reads site metadata and deploy summaries. Build logs remain in the Netlify UI; MrCron deep-links to them.
- What triggers a failed-deploy alert?
- The next sync sees a deploy with state=error. Configure an alert rule to route the failure to any channel (email, Slack, Discord, webhook).