You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,11 +43,11 @@ This section outlines the metrics available under each Analytics app tab. Before
43
43
44
44
Below is a summary of each Analytics app tab.
45
45
46
-
### Traffic
46
+
### HTTP Traffic
47
47
48
48
#### Free plan
49
49
50
-
These metrics include legitimate user requests as well as crawlers and threats. The Traffic tab features the following panels:
50
+
These metrics include legitimate user requests as well as crawlers and threats. The HTTP Traffic tab features the following panels:
51
51
52
52
***Web Traffic** - Displays metrics for *Requests*, *Bandwidth*, and *Unique Visitors*. If you are using Cloudflare Workers, subrequests data will not be visible in zone Traffic Analytics. Instead, you can find subrequests analytics under the **Workers & Pages** tab in the **Overview** section. Refer to [Worker Analytics](/analytics/account-and-zone-analytics/analytics-with-workers/#worker-analytics) for more information.
53
53
***Web Traffic Requests by Country** - Is an interactive map that breaks down the number of requests by country. This panel also includes a data table for **Top Traffic Countries / Regions** that display the countries with the most number of requests (up to five, if the data exists).
@@ -56,19 +56,46 @@ These metrics include legitimate user requests as well as crawlers and threats.
56
56
57
57
:::note
58
58
59
-
Privacy-first Web Traffic Analytics are available on the Pro, Business,
59
+
Privacy-first HTTP Traffic Analytics are available on the Pro, Business,
60
60
and Enterprise plans.
61
61
:::
62
62
63
-
Analytics are based on Cloudflare's edge logs, with no need for third party scripts or trackers. The Traffic tab features the following metrics:
63
+
Analytics are based on Cloudflare's edge logs, with no need for third party scripts or trackers. The HTTP Traffic tab features the following metrics:
64
64
65
-
***Requests** - An HTTP request. A typical page view requires many requests. If you are using Cloudflare Workers, subrequests data will not be visible in zone Traffic Analytics. Instead, you can find subrequests analytics under the **Workers & Pages** tab in the **Overview** section. Refer to [Worker Analytics](/analytics/account-and-zone-analytics/analytics-with-workers/#worker-analytics) for more information.
65
+
***Requests** - An HTTP request. A typical page view requires many requests. If you are using Cloudflare Workers, subrequests data will not be visible in zone HTTP Traffic Analytics. Instead, you can find subrequests analytics under the **Workers & Pages** tab in the **Overview** section. Refer to [Worker Analytics](/analytics/account-and-zone-analytics/analytics-with-workers/#worker-analytics) for more information.
66
66
***Data Transfer** - Total HTTP data transferred in responses.
67
67
* <aid="page-views" /> **Page views** - A page view is defined as a successful HTTP response with a content-type of HTML.
68
68
***Visits** - A visit is defined as a [page view](#page-views) that originated from a different website, or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
69
69
***API Requests** - An HTTP request for API data.
70
70
71
-
To receive more detailed metrics, **Add filter**. You can also filter each metric by **Referer**, **Host**, **Country**, **Path**, **Status code**, **Origin status code**, **Browser**, **Operating system**, or **Device type**.
71
+
To receive more detailed metrics, **Add filter**. You can also filter each metric by:
72
+
73
+
* Cache status
74
+
* Data center
75
+
* Source ASN
76
+
* Country
77
+
* Source device type
78
+
* Source IP
79
+
* Referer host
80
+
* Host
81
+
* HTTP method
82
+
* HTTP version
83
+
* Path
84
+
* Query string
85
+
* Content type
86
+
* Edge status code
87
+
* Origin status code
88
+
* Security Action
89
+
* Security Source
90
+
* Source browser
91
+
* Source operating system
92
+
* Source user agent
93
+
* X-Requested-With header
94
+
95
+
In addition, the following filters are available to Enterprise [Bot Management](/bots/get-started/bot-management/) customers only.
96
+
97
+
* Source JA4 fingerprint
98
+
* Source JA3 fingerprint
72
99
73
100
To change the time period, use the dropdown menu on the right-hand side above the graph. You can also drag to zoom on the graph.
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler.mdx
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,3 +199,25 @@ curl http://localhost:8600
199
199
```sh output
200
200
# -> user worker got "intercepted a request for customer-1 by the outbound" from fetch
201
201
```
202
+
203
+
## Remote dispatch namespaces
204
+
205
+
You can configure dispatch namespace bindings to connect to remote dispatch namespaces during local development by setting [`experimental_remote = true`](/workers/development-testing/#remote-bindings):
206
+
207
+
<WranglerConfig>
208
+
```jsonc title="wrangler.jsonc"
209
+
{
210
+
"dispatch_namespaces": [
211
+
{
212
+
"binding":"DISPATCH_NAMESPACE",
213
+
"namespace":"testing",
214
+
"experimental_remote":true
215
+
}
216
+
]
217
+
}
218
+
```
219
+
</WranglerConfig>
220
+
221
+
This allows you to run your [dynamic dispatch Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dynamic-dispatch-worker) locally, while connecting it to your remote dispatch namespace binding. You can then test changes to your core dispatching logic against real, deployed [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers).
222
+
223
+
For more information about remote bindings during local development, refer to [remote bindings documentation](/workers/development-testing/#remote-bindings).
Copy file name to clipboardExpand all lines: src/content/docs/d1/observability/debug-d1.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,4 +94,4 @@ You should include as much of the following in any bug report:
94
94
95
95
* Learn [how to debug Workers](/workers/observability/).
96
96
* Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
97
-
* Use [`wrangler dev`](/workers/wrangler/commands/#dev) to run your Worker and D1 locally and [debug issues before deploying](/workers/local-development/).
97
+
* Use [`wrangler dev`](/workers/wrangler/commands/#dev) to run your Worker and D1 locally and [debug issues before deploying](/workers/development-testing/).
Configuration and Log searches are also available via a public API.
9
+
10
+
## Authentication
11
+
12
+
Log Explorer is available to users with the following permissions:
13
+
14
+
-**Logs Edit**: users with Logs Edit permissions can enable datasets.
15
+
-**Logs Read**: users with Logs Read permissions can run queries via the UI or API.
16
+
17
+
Note that these permissions exist at the account and zone level and you need the appropriate permission level for the datasets you wish to query.
18
+
19
+
Authentication with the API can be done via an API token or API key with an email. Refer to [Create API token](/fundamentals/api/get-started/create-token/) for further instructions.
20
+
21
+
## Query data
22
+
23
+
Log Explorer includes a SQL API for submitting queries.
24
+
25
+
For example, to find an HTTP request with a specific [Ray ID](/fundamentals/reference/cloudflare-ray-id/), use the following SQL query:
--url-query query="SELECT CreatedAt, AppDomain, AppUUID, Action, Allowed, Country, RayID, Email, IPAddress, UserUID FROM access_requests WHERE Date >= '2025-02-06' AND Date <= '2025-02-06' AND CreatedAt >= '2025-02-06T12:28:39Z' AND CreatedAt <= '2025-02-06T12:58:39Z'"
58
+
```
59
+
60
+
This command returns the following request details:
0 commit comments