VergeCloud's Advanced Analytics gives you a detailed view of everything happening across your CDN. Instead of broad summaries, it breaks down traffic behavior, security events, and individual request activity into three focused sections: Data Transfer, Security, and Request Inspector.
This article covers what each section does and how to use it effectively.
The Data Transfer section provides visibility into bandwidth usage across your CDN. It helps you understand how much data was served, where it was delivered, how effectively content was cached, and which resources are driving traffic.
You can filter data by date range, granularity, status, URL, host, country, referer, IP, cache status, device, operating system, and browser.
The Total Data Transfer card shows the total volume of data served during the selected time period.
The Cache Status card breaks that traffic down by cache outcome, including HIT, MISS, REVALIDATED, BYPASS, EXPIRED, and UPDATING. The Egress Over Time graph complements these metrics by showing how traffic changed throughout the selected window, making it easy to identify spikes, drops, or unusual patterns.
This chart shows the countries generating the highest volume of egress traffic. It provides a quick view of where your content is being consumed and can help identify unexpected traffic concentrations or regional traffic spikes.
These views help you understand what is driving bandwidth consumption.
Together, these reports help identify high-traffic content, heavily utilized edge locations, and key traffic sources.
These tables provide additional insight into traffic behavior.
These views are particularly useful when investigating unexpected bandwidth usage or validating traffic trends observed elsewhere in the dashboard.
The Requests section provides visibility into request volume and traffic patterns across your domain. It helps you understand who is accessing your application, which resources are being requested, where traffic is coming from, and how requests are being handled at the edge.
You can filter data by date range, status, URL, host, country, referer, IP, cache status, device type, operating system, browser, and ASN.
The Total Requests card shows the total number of requests received during the selected period.
The Cache Status card breaks requests down by cache outcome, while the Requests Over Time graph helps identify traffic spikes, drops, and unusual activity patterns.
This chart shows the countries generating the highest number of requests, helping you understand traffic distribution and identify unexpected regional activity.
These reports help identify where requests are going and where they are coming from.
Together, these views help identify popular content, key traffic sources, and request distribution across your infrastructure.
These reports provide insight into the clients accessing your application.
These reports help analyze request behavior and traffic sources.
These views are particularly useful when investigating unusual traffic patterns, identifying bots, or troubleshooting application issues.
The Security section provides visibility into security events detected across your domain, including Firewall, WAF, DDoS, and Rate Limiting activity.
You can filter data by date range, URL, host, country, IP, referer, device, browser, and other dimensions to focus on specific traffic patterns or incidents.
The Security Threats graph shows blocked, challenged, and suspicious requests over time, while the Block Enforcement Breakdown highlights which security mechanism (Firewall, WAF, or Rate Limiting) took action.
This table lists the latest requests that triggered a security action. For each event, you can view details such as the source IP, requested URI, firewall action, matched rules, DDoS status, and rate limit action. Selecting View Detail opens the complete request information.
This section helps identify the main sources of security activity by showing the top URIs, source IPs, and ASNs associated with blocked, challenged, or suspicious traffic.
The Firewall section shows which firewall rules matched the most requests and how traffic was distributed across actions such as Allow, Bypass, Challenge, and Deny.
The WAF section provides a breakdown of WAF decisions and the most frequently triggered WAF rules, helping you understand the types of application-layer threats being detected.
This section highlights requests affected by DDoS protection and rate limiting, making it easier to identify excessive traffic patterns and mitigation actions.
The Request Inspector shows you raw CDN log rows for whatever time window and filters you have set. Think of it as a searchable, filterable view directly into what your edge is seeing. No log exports, no third party tools.
The filter bar at the top lets you narrow down requests quickly. You can combine any of these together:
The table search bar lets you search across URI, request ID, IP, user agent, and referer all at once.
Each row in the Requests table shows the timestamp, method, URI, status code, status label, cache status, bytes sent, and IP.
Where this actually helps:
The three sections work best when used together. A common workflow is to start with the Security section when something looks off, identify the time window and type of activity, and then switch to the Request Inspector to look at the specific requests involved. The Data Transfer section can then tell you whether that activity had any impact on bandwidth or cache performance.
For day to day monitoring, a quick look at the Security section can catch unusual spikes in blocked traffic before they become a bigger issue. The Data Transfer section helps you keep tabs on caching behavior over time. The Request Inspector is there when you need to go from a high level observation down to a specific request.
Advanced Analytics gives you three different lenses to look at your CDN traffic. Data Transfer shows bandwidth usage and cache performance. Security surfaces what your WAF, rate limiting, and bot protection rules are catching. Request Inspector lets you get into the actual log rows when you need to understand exactly what happened at the edge.
Used together, they cover most investigation and monitoring needs without leaving the dashboard.