Analytics Tab
When requests pass through the Cloudflare network, many data points are captured associated with HTTP traffic, encryption, security, DNS, and Workers. The resulting metrics appear in analytics products, including our dashboard UI and APIs.
It is further divided into 5 sections :
1) Traffic
Web Traffic → We get all information here related to Web Traffic in a graph format.
Web Traffic Requests by Country → We also get information of web traffic requests by country. This is displayed in map format.
Top Traffic Countries / Regions -> We also get information about traffic per country/region in table format.
Share your stats → Here we can share the stats on twitter.
2) Security
Threats - It provides threats related information in graph format. We are not seeing it here because we don't have any threat in last 24 hours.
Threats by country - We also get information of threats requests by country. This is displayed in map format. Example of how it looks.
Top Threats Countries/Regions
Top Crawlers/Bots
We get information related to it in table format. Example of screenshot how it looks like.
Rate Limiting - We will study about it when we will be on firewall section.
Overview
(i) Total Threats Stopped → Total Threats Stopped measures the number of “suspicious” and “bad” requests that were aimed at your website. Requests receive these labels by our IP Reputation Database as they enter Cloudflare’s network:
Legitimate: request pass directly to your website
Suspicious: request has been challenged with a CAPTCHA page or JavaScript challenge page
Bad: request has been blocked due to IP Access Rules or Browser Integrity Check (BIC)
(ii) Traffic Served Over SSL → This chart shows the division between unencrypted and encrypted ‘HTTPS’ requests using TLS. Redirects from HTTP to HTTPS are counted as unencrypted requests. When a page rule or origin server redirect to HTTPS is used, a percentage of unencrypted traffic is normal.
(iii) Types of threats Mitigated → Cloudflare classifies each of the threats that it blocks or challenges. For example - It can be Bad browser, Bad IP and so on. If cloudflare is not able to classify the treat it marks it as unclassified.
3) Performance
(i) Origin Performance (Argo) - We can see the analytics related to Argo here. Argo is a service that uses optimized routes across the Cloudflare network to deliver responses to users more quickly, reliably, and securely. We will study about it when we will in Traffic Tab. It is a paid service.
We don't see anything here because Argo is not enabled on this site and we will look into it when we will on Traffic Tab.
(ii) Overview
a) Client HTTP Version Used → This chart shows the mix of HTTP versions your visitors used to request content from Cloudflare. Possible values include HTTP/1.0, HTTP/1.1, HTTP/2, HTTP/3.
b) Bandwidth Saved → This shows the bandwidth saved by Cloudflare by serving cached versions of your content from our data centers. This means that only a small number of requests actually go back to your origin server.
c) Content Type Breakdown ->This represents the breakdown by content type of all traffic flowing through Cloudflare for site (including both cached and uncached responses).The classifications include:“jpeg”, “html”, “png”, “gif”, “css”, “javascript”, “json”, “octet-stream”, “plain”, “ocsp-response”, “x-shockwave-flash”, “xml”, “mixed”, “jpg”, “svg”, “webp”.
Note: For “empty” there was either no content type header or the content header was empty.
4) DNS
HAS TO CREATE NOTES FOR IT.
5) Workers - We have no graph here because we have not created any worker yet. We will look into it when we will on worker tab.
