Merge branch 'production' into w-changelogs

Oxyjun · web-flow · commit 40bc9fe0d2cc · 2025-04-09T13:32:58.000+01:00
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -36,7 +36,7 @@
 		"@astrojs/starlight-docsearch": "0.6.0",
 		"@astrojs/starlight-tailwind": "3.0.1",
 		"@astrojs/tailwind": "5.1.5",
-		"@cloudflare/vitest-pool-workers": "0.8.12",
+		"@cloudflare/vitest-pool-workers": "0.8.14",
 		"@cloudflare/workers-types": "4.20250404.0",
 		"@codingheads/sticky-header": "1.0.2",
 		"@expressive-code/plugin-collapsible-sections": "0.40.2",
@@ -50,7 +50,7 @@
 		"@types/node": "22.14.0",
 		"@types/react": "19.0.7",
 		"@types/react-dom": "19.0.4",
-		"@typescript-eslint/parser": "8.29.0",
+		"@typescript-eslint/parser": "8.29.1",
 		"algoliasearch": "5.23.3",
 		"astro": "5.6.1",
 		"astro-breadcrumbs": "3.3.1",
@@ -75,7 +75,7 @@
 		"he": "1.2.0",
 		"jsonc-parser": "3.3.1",
 		"lz-string": "1.5.0",
-		"marked": "15.0.7",
+		"marked": "15.0.8",
 		"mdast-util-from-markdown": "2.0.2",
 		"mdast-util-mdx": "3.0.0",
 		"mdast-util-mdx-expression": "2.0.1",
diff --git a/src/assets/images/changelog/rules/snippets-ga-trace.gif b/src/assets/images/changelog/rules/snippets-ga-trace.gif
diff --git a/src/assets/images/changelog/rules/snippets-ga.png b/src/assets/images/changelog/rules/snippets-ga.png
diff --git a/src/assets/images/changelog/workers/observability/2025-04-09-query-builder-investigate.png b/src/assets/images/changelog/workers/observability/2025-04-09-query-builder-investigate.png
diff --git a/src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png b/src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png
diff --git a/src/content/changelog/rules/2025-04-09-snippets-ga.mdx b/src/content/changelog/rules/2025-04-09-snippets-ga.mdx
@@ -6,6 +6,8 @@ products:
 date: 2025-04-09T14:00:00Z
 ---
 
+![Cloudflare Snippets are now GA](~/assets/images/changelog/rules/snippets-ga.png)
+
 [Cloudflare Snippets](/rules/snippets/) are now generally available at no extra cost across all paid plans — giving you a fast, flexible way to programmatically control HTTP traffic using lightweight JavaScript.
 
 You can now use Snippets to modify HTTP requests and responses with confidence, reliability, and scale. Snippets are production-ready and deeply integrated with Cloudflare Rules, making them ideal for everything from quick dynamic header rewrites to advanced routing logic.
@@ -15,6 +17,8 @@ What's new:
 - **Snippets are now GA** – Available at no extra cost on all Pro, Business, and Enterprise plans.
 - **Ready for production** – Snippets deliver a production-grade experience built for scale.
 - **Part of the Cloudflare Rules platform** – Snippets inherit request modifications from other Cloudflare products and support sequential execution, allowing you to run multiple Snippets on the same request and apply custom modifications step by step.
-- **Trace integration (rolling out)** – Use [Cloudflare Trace](/fundamentals/trace-request/) to see which Snippets were triggered on a request — helping you understand traffic flow and debug more effectively.
+- **Trace integration** – Use [Cloudflare Trace](/fundamentals/trace-request/) to see which Snippets were triggered on a request — helping you understand traffic flow and debug more effectively.
+
+  ![Snippets shown in Cloudflare Trace results](~/assets/images/changelog/rules/snippets-ga-trace.gif)
 
 Learn more in the [launch blog post](https://blog.cloudflare.com/snippets/).
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -0,0 +1,50 @@
+---
+title: Investigate your Workers with the Query Builder in the new Observability dashboard
+description: Workers Observability now offers a Query Builder to help developers construct structured queries to investigate their telemtry data.
+products:
+  - workers
+date: 2025-04-09T00:00:00Z
+hidden: false
+---
+
+import { WranglerConfig } from "~/components"
+
+The [Workers Observability dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](/workers/observability/logs/workers-logs).
+
+The **Overview** tab shows logs from all your Workers in one place. The **Invocations** view groups logs together by invocation, which refers to the specific trigger that started the execution of the Worker (i.e. fetch). The **Events** view shows logs in the order they were produced, based on timestamp. Previously, you could only view logs for a single Worker.
+
+![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-workers-observability-overview.png)
+
+The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:
+- Which paths are experiencing the most 5XX errors?
+- What is the wall time distribution by status code for my Worker?
+- What are the slowest requests, and where are they coming from?
+- Who are my top N users? 
+
+![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-query-builder.png)
+
+The Query Builder can use any field that you store in your logs as a key to visualize, filter, and group by. Use the Query Builder to quickly access your data, build visualizations, save queries, and share them with your team. 
+
+### Workers Logs is now Generally Available
+
+[Workers Logs](/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.
+
+We've introduced a number of changes during our beta period, including:
+- Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
+- Performance improvements to ensure no adverse impact
+- Public [API endpoints](https://developers.cloudflare.com/api/resources/workers/subresources/observability/) for broader consumption
+
+The API documents three endpoints: list the keys in the telemetry dataset, run a query, and list the unique values for a key. For more, visit our [REST API documentation](https://developers.cloudflare.com/api/resources/workers/subresources/observability/).
+
+Visit the [docs](/workers/observability/query-builder) to learn more about the capabilities and methods exposed by the Query Builder. Start using Workers Logs and the Query Builder today by enabling observability for your Workers:
+
+<WranglerConfig>
+	```toml
+	[observability]
+	enabled = true
+
+	[observability.logs]
+	invocation_logs = true
+	head_sampling_rate = 1 # optional. default = 1.
+	```
+</WranglerConfig>
diff --git a/src/content/changelog/workers/2025-04-09-workers-timing.mdx b/src/content/changelog/workers/2025-04-09-workers-timing.mdx
@@ -4,6 +4,7 @@ description: Workers Observability tooling now shows CPU time and Wall time for
 products:
   - workers
 date: 2025-04-09T00:00:00Z
+
 ---
 
 You can now observe and investigate the CPU time and Wall time for every Workers Invocations.
diff --git a/src/content/docs/agents/api-reference/agents-api.mdx b/src/content/docs/agents/api-reference/agents-api.mdx
@@ -615,34 +615,34 @@ class AgentClient extends PartySocket {
 import { AgentClient } from "agents/client";
 
 // Connect to an Agent instance
-const socket = new AgentClient({
+const client = new AgentClient({
   agent: "chat-agent", // Name of your Agent class in kebab-case
   name: "support-room-123", // Specific instance name
+  host: window.location.host, // Using same host
+});
 
-  // Optional event handlers
-  onOpen: () => {
-    console.log("Connected to agent");
-    // Send an initial message
-    socket.send(JSON.stringify({ type: "join", user: "user123" }));
-  },
+client.onopen = () => {
+  console.log("Connected to agent");
+  // Send an initial message
+  client.send(JSON.stringify({ type: "join", user: "user123" }));
+};
 
-  onMessage: (event) => {
-    // Handle incoming messages
-    const data = JSON.parse(event.data);
-    console.log("Received:", data);
+client.onmessage = (event) => {
+	// Handle incoming messages
+	const data = JSON.parse(event.data);
+	console.log("Received:", data);
 
-    if (data.type === "state_update") {
-      // Update local UI with new state
-      updateUI(data.state);
-    }
-  },
+	if (data.type === "state_update") {
+		// Update local UI with new state
+		updateUI(data.state);
+	}
+};
 
-  onClose: () => console.log("Disconnected from agent")
-});
+client.onclose = () => console.log("Disconnected from agent");
 
 // Send messages to the Agent
 function sendMessage(text) {
-  socket.send(JSON.stringify({
+  client.send(JSON.stringify({
     type: "message",
     text,
     timestamp: Date.now()
diff --git a/src/content/docs/magic-network-monitoring/cloud-flow-logs.mdx b/src/content/docs/magic-network-monitoring/cloud-flow-logs.mdx
@@ -0,0 +1,15 @@
+---
+title: Cloud flow logs (beta)
+pcx_content_type: reference
+sidebar:
+  order: 5
+  label: Cloud flow logs
+  badge:
+    text: Beta
+---
+
+Customers using Magic Network Monitoring can export virtual private cloud (VPC) flow logs from their cloud environment to Cloudflare's network. Cloudflare will then process these VPC flow logs and display analytics on your cloud traffic in the dashboard. Customers can also ingest data on their cloud traffic via our public GraphQL API which powers the cloud traffic analytics in the dashboard.
+
+Currently, Magic Network Monitoring only supports AWS VPC flow logs via AWS Firehose. AWS VPC flow logs can only be configured via Cloudflare's API for Magic Network Monitoring.
+
+To learn how to set up this feature, refer to [VPC flow log guide (beta)](/magic-network-monitoring/get-started/#vpc-flow-log-guide).
diff --git a/src/content/docs/magic-network-monitoring/get-started.mdx b/src/content/docs/magic-network-monitoring/get-started.mdx
@@ -5,19 +5,24 @@ sidebar:
   order: 2
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { APIRequest, Badge, GlossaryTooltip } from "~/components";
 
-To begin using Magic Network Monitoring, complete the list of tasks below.
+To begin using Magic Network Monitoring for network and/or cloud traffic visibility, complete the list of tasks below.
+
+- [NetFlow and sFlow guide](#netflow-and-sflow-guide)
+- [VPC flow log guide (beta)](#vpc-flow-log-guide)
 
 If you are an Enterprise customer, Cloudflare can significantly accelerate the onboarding timeline during active-attack scenarios. Enterprise customers that would like to use Magic Network Monitoring and Magic Transit On Demand together can begin by [configuring Magic Transit](/magic-transit/get-started/).
 
-## 1. Verify NetFlow or sFlow capabilities
+## NetFlow and sFlow guide
+
+### 1. Verify NetFlow or sFlow capabilities
 
 Verify your routers are capable of exporting <GlossaryTooltip term="NetFlow">NetFlow</GlossaryTooltip> or <GlossaryTooltip term="sFlow">sFlow</GlossaryTooltip> to an IP address on Cloudflare's network. Magic Network Monitoring supports NetFlow v5, NetFlow v9, IPFIX, and sFlow.
 
 Refer to [Supported routers](/magic-network-monitoring/routers/supported-routers) to view a list of supported routers. The list is not exhaustive.
 
-## 2. Register your router with Cloudflare
+### 2. Register your router with Cloudflare
 
 When you register your router with Cloudflare, your router links your NetFlow or sFlow data to your Cloudflare account.
 
@@ -29,7 +34,7 @@ When you register your router with Cloudflare, your router links your NetFlow or
 6. Under **Default router sampling rate**, enter a value for the <GlossaryTooltip term="sampling">sampling</GlossaryTooltip> rate. The value should match the sampling rate of your NetFlow or sFlow configuration.
 7. Select **Next**.
 
-## 3. Configure your router
+### 3. Configure your router
 
 Next, configure your router to send NetFlow/SFlow data to Cloudflare. For this step, you will also need to have your router's configuration menu open to input the values shown in the Cloudflare dashboard.
 
@@ -40,7 +45,7 @@ Refer to the [NetFlow/IPFIX configuration](/magic-network-monitoring/routers/net
 3. Enter the values shown in your router's configuration.
 4. Select **Next**.
 
-## 4. Check your router configuration
+### 4. Check your router configuration
 
 After setting up your router, confirm the configuration was successfully set up.
 
@@ -54,6 +59,40 @@ When you are done with router configuration, select **Finish onboarding**.
 This will only be visible during the onboarding process. When you are finished onboarding, this page will no longer be visible.
 :::
 
-## 5. Create rules
+### 5. Create rules
 
 Create rules to analyze data for a specific set of destinations or to implement thresholds. Refer to [Rules](/magic-network-monitoring/rules/) for more information.
+
+## VPC flow log guide <Badge text="Beta" variant="caution" />
+
+### 1. Verify cloud flow log capabilities
+
+Verify that your AWS account is capable of exporting AWS VPC flow logs via AWS Firehose. Currently, Magic Network Monitoring only supports VPC flow log ingestion for AWS.
+
+### 2. Set up AWS Firehose to export VPC flow logs to Cloudflare
+
+:::note
+AWS VPC flow logs can only be configured via the Cloudflare API for Magic Network Monitoring. There are no inputs in the dashboard for configuring AWS VPC flow logs.
+:::
+
+1. Create an authorization token via [Cloudflare's API for Magic Network Monitoring](/api/resources/magic_network_monitoring/subresources/vpc_flows/subresources/tokens/methods/create/). This authorization token allows Cloudflare to identify and verify the account sending VPC flow logs to our endpoint.
+
+	<APIRequest
+		path="/accounts/{account_id}/mnm/vpc-flows/token"
+		method="POST"
+	/>
+
+2. Set the `HTTP Headers - X-Amz-Firehose-Access-Key` in the stream configuration for the authorization token generated in the previous step.
+
+3. Send your AWS Firehose VPC flow log stream towards `https://aws-flow-logs.cloudflare.com/`.
+
+4. Select all of the AWS VPC flow log data fields that you want to send to Cloudflare. You should select the highest number AWS VPC flow log version that supports all the fields you want to export to Cloudflare (refer to [AWS flow log documentation](https://docs.aws.amazon.com/vpc/latest/userguide/flow-log-records.html) for more information). For example, if you need a version 8 field like `reject-reason`, you must export all fields from versions 1 through 8. Cloudflare supports all seven templates for AWS VPC Flow logs.
+
+### 3. Verify your cloud traffic via analytics
+
+After setting up AWS Firehose to send VPC flow logs to Magic Network Monitoring, you can confirm that Cloudflare is receiving the logs as expected by searching for your cloud traffic data in the analytics page of the Magic Network Monitoring dashboard.
+
+1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. Go to **Analytics & Logs** > **Magic Monitoring**.
+
+The default view will be the analytics dashboard for Magic Network Monitoring.
diff --git a/src/content/docs/magic-network-monitoring/index.mdx b/src/content/docs/magic-network-monitoring/index.mdx
@@ -20,13 +20,13 @@ import {
 
 <Description>
 
-Improve your network visibility and detect DDoS attacks based on traffic flows.
+Improve your network and cloud traffic visibility. Customers with public IPs can also detect DDoS attacks based on their traffic flows.
 
 </Description>
 
 <Plan type="all" />
 
-Magic Network Monitoring provides visibility into your network traffic by analyzing network <GlossaryTooltip term="flow data">flow data</GlossaryTooltip> sent from a customer's routers. Magic Network Monitoring supports NetFlow v5, NetFlow v9, IPFIX, and sFlow.
+Magic Network Monitoring provides visibility into your network traffic and cloud traffic by analyzing network <GlossaryTooltip term="flow data">flow data</GlossaryTooltip> sent from a customer's routers or cloud environment. Magic Network Monitoring supports NetFlow v5, NetFlow v9, IPFIX, and sFlow. In cloud environments, Magic Network Monitoring supports AWS VPC flow logs via AWS Firehose.
 
 Magic Network Monitoring is generally available to everyone with a Cloudflare account by default. You can log in to your Cloudflare dashboard, select your account, then go to **Analytics & Logs** > **Magic Monitoring** to get started.
 
diff --git a/src/content/docs/magic-network-monitoring/tutorials/index.mdx b/src/content/docs/magic-network-monitoring/tutorials/index.mdx
@@ -2,7 +2,7 @@
 title: Tutorials
 pcx_content_type: navigation
 sidebar:
-  order: 5
+  order: 6
   group:
     hideIndex: true
 
diff --git a/src/content/docs/rules/snippets/index.mdx b/src/content/docs/rules/snippets/index.mdx
@@ -1,19 +1,18 @@
 ---
 pcx_content_type: concept
-title: Snippets
+title: Cloudflare Snippets
 sidebar:
   order: 4
   group:
-    badge:
-      text: Beta
+    label: Snippets
 head:
   - tag: title
-    content: Cloudflare Snippets (beta)
+    content: Cloudflare Snippets
 ---
 
 import { FeatureTable, GlossaryTooltip, Render, Card } from "~/components";
 
-Cloudflare Snippets (beta) provide a powerful and flexible way to customize the behavior of your website or application using short pieces of JavaScript code. With Snippets, you can modify HTTP response headers, implement <GlossaryTooltip term="JSON web token (JWT)" prepend="JSON web token (JWT) is ">JWT</GlossaryTooltip> validation, perform complex <GlossaryTooltip term="redirect">redirects</GlossaryTooltip>, and much more.
+Cloudflare Snippets provide a powerful and flexible way to customize the behavior of your website or application using short pieces of JavaScript code. With Snippets, you can modify HTTP response headers, implement <GlossaryTooltip term="JSON web token (JWT)" prepend="JSON web token (JWT) is ">JWT</GlossaryTooltip> validation, perform complex <GlossaryTooltip term="redirect">redirects</GlossaryTooltip>, and much more.
 
 For code samples addressing common use cases, please refer to the [Examples](/rules/snippets/examples/) section.
 
@@ -47,6 +46,8 @@ If you have used the Cloudflare API to create a code snippet that is not associa
 
 Each <GlossaryTooltip term="Snippets subrequest" prepend="A subrequest is ">subrequest</GlossaryTooltip> in a redirect chain counts against the subrequest limit. This means that if a subrequest was redirected it would count as two subrequests. To avoid issues, ensure that you make a subrequest to the end location of the redirect chain.
 
+Currently, [Version Management](/version-management/) does not support Snippets.
+
 ## Limits
 
 Cloudflare Snippets are designed for fast, lightweight edge logic. The following limits apply:
diff --git a/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx b/src/content/docs/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips.mdx
@@ -421,7 +421,7 @@ As this plugin was created by an outside party, we can't provide technical suppo
 
 If you use the hosting control panel VestaCP, you have both Nginx and Apache running on your server. Requests are proxied through Nginx before going to Apache.
 
-Because of this Nginx proxy, you actually need to the instructions to configure Nginx to return the real visitor IP address. [mod_remoteip](https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html) for Apache is not needed unless you disable the Nginx server for some requests. Adding [mod_remoteip](https://support.cloudflare.com/hc/articles/200170786#C5XWe97z77b3XZV) to Apache will not conflict with the Nginx server configuration.
+Because of this Nginx proxy, you actually need to follow the instructions to configure Nginx to return the real visitor IP address. [mod_remoteip](https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html) for Apache is not needed unless you disable the Nginx server for some requests. Adding [mod_remoteip](https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html) to Apache will not conflict with the Nginx server configuration.
 
 ### node.js
 
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -5,9 +5,6 @@ head: []
 description: Store, filter, and analyze log data emitted from Cloudflare Workers.
 sidebar:
   order: 2
-  badge:
-    variant: tip
-    text: New
 
 ---
 
diff --git a/src/content/partials/version-management/product-limitations.mdx b/src/content/partials/version-management/product-limitations.mdx
@@ -50,7 +50,7 @@ Version Management does not currently support or have limited support for the fo
 
 <Details header="Cloudflare API">
 
-- Zone Version Management does not currently expose a public [API](/api/).
+- Version Management does not currently expose a public [API](/api/).
 - Customers can only use Version Management through the [Cloudflare dashboard](https://dash.cloudflare.com/).
 
 </Details>
@@ -80,6 +80,12 @@ Version Management does not currently support or have limited support for the fo
 
 </Details>
 
+<Details header="Rules">
+
+- Version Management does not currently support [Snippets](/rules/snippets/).
+
+</Details>
+
 <Details header="Security Insights">
 
 - [Security Insights](/security-center/security-insights/) are not shown when Zone Versioning is enabled and the first version is deployed to production.
@@ -88,7 +94,7 @@ Version Management does not currently support or have limited support for the fo
 
 <Details header="Terraform">
 
-- Zone Version Management does not currently support [Terraform](/terraform/).
+- Version Management does not currently support [Terraform](/terraform/).
 - Customers should either use Terraform or Version Management.
 
 </Details>
diff --git a/src/content/plans/index.json b/src/content/plans/index.json
@@ -1318,7 +1318,7 @@
 			}
 		},
 		"snippets": {
-			"title": "Snippets (beta)",
+			"title": "Snippets",
 			"link": "/rules/snippets/",
 			"properties": {
 				"availability": {
