The Cloudflare integration feeds Server Log Monitoring straight from the edge. VitalSentinel deploys a small Worker on your own Cloudflare account, on the zone of your domain, and it forwards each request's log line as your server answers it. You see which search engine and AI crawlers hit your site, what they asked for and how your server responded, minutes after it happens.
What You Get
Real-Time Crawler Data
Every Googlebot, Bingbot and AI crawler hit arrives as it happens, not on a daily file schedule. The first request is usually confirmed within about five minutes of arriving.
Every Plan, Free Included
The Worker is the one log source available on the Free plan. It collects at the rate your site is actually crawled, up to your plan's monthly bot hits: 500K on Free, 3M on Starter, 10M on Lite, 50M on Standard and 150M on Advanced.
Automatic Domain Verification
A connected zone that is active on Cloudflare also proves you own the domain, which Site Health Monitoring and Page Monitoring need before they start.
Safe by Design
The route fails open: if the Worker fails, your site keeps working and only log collection pauses. The Worker is unique to your domain and no other Worker on the account is touched.
What Is Collected
Only crawler traffic is kept: search engines, AI training and AI search crawlers, AI assistants and AI agents. SEO tools, link previews, uptime checkers and any client that gives no name are dropped on arrival and only counted, and human visitors are never collected by Server Log Monitoring. Query-parameter names are stored, never their values, and the IP addresses of unverified or spoofed requests are never stored.
How to Connect
You need a Cloudflare API token from My Profile → API Tokens → Create Token → Custom Token, scoped to exactly these three permissions:
- Account → Workers Scripts: Edit
- Zone → Workers Routes: Edit
- Zone → Zone: Read
Your domain must be a zone on the same Cloudflare account. Then, in VitalSentinel:
Cost on your Cloudflare bill
- The Worker runs on your Cloudflare account, so Cloudflare charges you for it, roughly $0.30 per million requests the Worker runs on. The wizard estimates the monthly cost from your zone's own traffic before you deploy.
- On Cloudflare's Workers Free plan, Cloudflare stops running a Worker for the rest of the day once it passes the daily request cap. Your site stays up; log collection resumes the next day. The wizard warns you when your traffic is above that cap.
- Prefer to keep it off your Cloudflare bill? On paid plans you can connect an SFTP, Amazon S3, Cloudflare R2 or Google Cloud Storage log source instead, for the same dashboards on a daily cadence.
Letting VitalSentinel Bot Through Cloudflare
If Cloudflare's WAF or Bot Fight Mode blocks our crawler, Site Health Monitoring shows the exact steps in its crawler access settings. In short: in Security → WAF, add a custom rule where the user agent contains VitalSentinel Bot and the source IP is in our published list, set the action to Skip, and move the rule to the top. Bot Fight Mode and Super Bot Fight Mode need their own exception.
Privacy & Security
- The API token is checked at every step and stored encrypted only after the Worker deploys. Only its prefix is ever shown back.
- Ask for exactly the three permissions above. Narrower is safer, and it is all this integration needs.
- Disconnect removes the Worker route, the Worker script and our encrypted copy of the token. The token itself stays valid until you revoke it in Cloudflare.
For every setup detail, see the log source guide and domain verification with Cloudflare.
