Monitoring & Analytics
Monitor Your Websites. Understand Their Visitors.
Two different questions: is the site up and answering correctly? and how do people actually use it? Nodekeeper answers the first on every plan, including Free. From Personal, it adds self-hosted visitor analytics, heatmaps, session replay and geographic reports — collected on your own servers, not sent to a third-party analytics service.
Is the website working? All plans, including Free
Website and system monitoring is part of the free base: you do not need a paid plan to know when a site or service stops answering.
HTTP / HTTPS checks
Expected status code, response time and an optional keyword that must appear in the page — so "200 but broken" is caught too.
TCP port and ping
Check that a database, SSH or any other port is open, or that a host answers ICMP ping.
DNS checks
Resolve a record (A, AAAA or TXT) and notice when it stops resolving.
Alerts without noise
A check is marked down only after several consecutive failures (3 by default), and you get a recovery notice when it comes back. Notifications go to email or a webhook.
- Checks run from your own node. Probing the same target from several nodes in different regions uses sync groups, which are in Business.
- Operation records are written on every plan. The website-log and WAF-log viewers in the panel start at Personal.
How do visitors use it? From Personal
A site can be up and still lose visitors. Personal adds the tools to see where they come from, what they click and where they leave.
JS website analytics
A small script on your pages reports page views and sessions.
- Timeline and top pages, referrers and devices
- Custom events, goals and funnels
- Real-time view
- Per-site tracking for sites on your nodes, or a standalone property with its own script snippet for a website served elsewhere
Heatmaps
See where clicks concentrate on a page. Heatmaps are off by default and are switched on per site, only where you want them.
Session replay
Replay a visit to understand a confusing form or a broken step. Replay is off by default per site.
- By default only password fields are masked. Mask any other field (names, emails, addresses, messages) with your own CSS selectors before enabling replay.
- Do not enable replay on login, payment, mailbox or web-terminal pages.
IP geo / city data
Country and city distribution of visits, estimated from IP addresses.
- IP geolocation is an estimate of a network location — not GPS and not a person’s identity. VPNs, mobile networks and proxies move it.
- ISP, domain and connection-type fields need a commercial MaxMind GeoIP2 database.
Stop abnormal traffic, not only count it From Personal
Abnormal traffic handling uses the same edge that serves the site: request rate limits, IP and GeoIP rules, a human check on the CDN edge, and JA3 TLS-fingerprint blocking. The base ModSecurity WAF rule sets stay in Free All plans, including Free.
Read more: Security · IP / CIDR rule sets · GeoIP rules · JA3 fingerprints
What the numbers mean
JS analytics is not server traffic
Only browsers that run the script are counted. Script blockers, disabled JavaScript, bots and your own filter rules all change the numbers. Use it to understand behaviour, not as a bandwidth or billing total.
Your data stays with you
Events are collected and aggregated on your own Nodekeeper master node. You decide where the servers are and how long you keep data.
Record less, not more
Turn heatmaps and replay on only where they answer a question, keep them off sensitive pages, and tell your visitors as your local rules require.
Free and Personal, side by side
| Capability | Free | Personal and up |
|---|---|---|
| Connectivity checks: HTTP(S), TCP, ping, DNS, with alerts | ✓ | ✓ |
| Base ModSecurity WAF | ✓ | ✓ |
| Operation records | ✓ (written) | ✓ + website-log and WAF-log viewers |
| JS analytics, events, goals, funnels, real-time | — | ✓ |
| Heatmaps and session replay (off by default) | — | ✓ |
| IP-based country / city reports | — | ✓ |
| Rate limits, IP / GeoIP rules, human check, JA3 blocking | — | ✓ |
| Probing from several regions | — | Business |
Billed per node. Prices and the full comparison are on the pricing page.