Merge branch 'cloudflare:production' into production

Author: krishnprakash

src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx

@@ -0,0 +1,28 @@
+---
+title: Gain visibility into user actions in Zero Trust Browser Isolation sessions
+description: User action logs for Remote Browser Isolation
+date: 2025-03-04T11:00:00Z
+---
+
+We're excited to announce that new logging capabilities for [Remote Browser Isolation (RBI)](/cloudflare-one/policies/browser-isolation/) through [Logpush](/logs/reference/log-fields/account/) are available in Beta starting today!
+
+With these enhanced logs, administrators can gain visibility into end user behavior in the remote browser and track blocked data extraction attempts, along with the websites that triggered them, in an isolated session.
+
+```json
+{
+	"AccountID": "$ACCOUNT_ID",
+	"Decision": "block",
+	"DomainName": "www.example.com",
+	"Timestamp": "2025-02-27T23:15:06Z",
+	"Type": "copy",
+	"UserID": "$USER_ID"
+}
+```
+
+User Actions available:
+
+- **Copy & Paste**
+- **Downloads & Uploads**
+- **Printing**
+
+Learn more about how to get started with Logpush in our [documentation](/logs/get-started/).

src/content/docs/ai-gateway/observability/logging/index.mdx

@@ -12,8 +12,7 @@ Logging is a fundamental building block for application development. Logs provid
 
 Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status, token usage, cost, and duration. These logs persist, giving you the flexibility to store them for your preferred duration and do more with valuable request data.
 
-You can store up to 10 million logs per gateway. If your limit is reached, new logs will stop being saved. To continue saving logs, you must delete older logs to free up space for new logs.
-
+By default, each gateway can store up to 10 million logs. You can customize this limit per gateway in your gateway settings to align with your specific requirements. If your storage limit is reached, new logs will stop being saved. To continue saving logs, you must delete older logs to free up space for new logs.
 To learn more about your plan limits, refer to [Limits](/ai-gateway/reference/limits/).
 
 We recommend using an authenticated gateway when storing logs to prevent unauthorized access and protects against invalid requests that can inflate log storage usage and make it harder to find the data you need. Learn more about setting up an [authenticated gateway](/ai-gateway/configuration/authentication/).
@@ -51,15 +50,23 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/
 '
 ```
 
+## Managing log storage
+
+To manage your log storage effectively, you can:
+- Set Storage Limits: Configure a limit on the number of logs stored per gateway in your gateway settings to ensure you only pay for what you need. 
+- Enable Automatic Log Deletion: Activate the Automatic Log Deletion feature in your gateway settings to automatically delete the oldest logs once the log limit you’ve set or the default storage limit of 10 million logs is reached. This ensures new logs are always saved without manual intervention.
+
 ## How to delete logs
 
+To manage your log storage effectively and ensure continuous logging, you can delete logs using the following methods:
+
 ### Automatic Log Deletion
 
-​To maintain continuous logging within your gateway's storage constraints, enable Automatic Log Deletion in your Gateway settings. This feature automatically deletes the oldest logs once the log limit you've set or the default storage limit of 10 million logs is reached, ensuring new logs are saved without manual intervention. Logs are deleted in increments of 0.1% of the storage limit, equating to 10,000 logs per deletion when using the default limit.​
+​To maintain continuous logging within your gateway's storage constraints, enable Automatic Log Deletion in your Gateway settings. This feature automatically deletes the oldest logs once the log limit you've set or the default storage limit of 10 million logs is reached, ensuring new logs are saved without manual intervention. 
 
 ### Manual deletion
 
-To manually delete logs, navigate to the Logs tab in the dashboard. Use the available filters such as status, cache, provider, cost, or any other options in the dropdown to refine the logs you wish to delete. Once filtered, select Delete logs to complete the action.
+To manually delete logs through the dashboard, navigate to the Logs tab in the dashboard. Use the available filters such as status, cache, provider, cost, or any other options in the dropdown to refine the logs you wish to delete. Once filtered, select Delete logs to complete the action.
 
 See full list of available filters and their descriptions below:
 
@@ -78,3 +85,7 @@ See full list of available filters and their descriptions below:
 | Metadata Value  | equals, does not equal                                       | specific metadata values.                 |
 | Log ID          | equals, does not equal                                       | a specific Log ID.                        |
 | Event ID        | equals, does not equal                                       | a specific Event ID.                      |
+
+### API deletion
+
+You can programmatically delete logs using the AI Gateway API. For more comprehensive information on the `DELETE` logs endpoint, check out the [Cloudflare API documentation](https://developers.cloudflare.com/api/resources/ai_gateway/subresources/logs/methods/delete/). 

src/content/docs/ai-gateway/reference/pricing.mdx

@@ -17,7 +17,7 @@ You can monitor your usage in the AI Gateway dashboard.
 
 :::note[Note]
 
-Billing for persistent logs has not yet started. Users on paid plans can store logs beyond the included volume of 200,000 logs stored a month without being charged during this period. (Users on the free plan remain limited to the 100,000 logs cap for their plan.) We will provide plenty of advanced notice before charging begins for persistent log storage. 
+Billing for persistent log storage will begin on April 15, 2025. Users on paid plans can store logs beyond the included volume of 200,000 logs stored a month without being charged until this date. Users on the free plan remain limited to the 100,000 logs cap for their plan. Please ensure your stored logs are within your plan's included volume before April 14, 2025, if you do not want to be charged. 
 
 :::
 
@@ -30,7 +30,7 @@ Persistent logs are available on all plans, with a free allocation for both free
 | Workers Free | 100,000 logs total | N/A – Upgrade to Workers Paid        |
 | Workers Paid | 200,000 logs total | $8 per 100,000 logs stored per month |
 
-Allocations are based on the total logs stored across all gateways. If your limit is reached, new logs will stop being saved. To continue saving logs, you must [delete logs](/ai-gateway/observability/logging/#how-to-delete-logs/) to free up space. 
+Allocations are based on the total logs stored across all gateways. For guidance on managing or deleting logs, please see our [documentation](/ai-gateway/observability/logging).
 
 ## Logpush
 

src/content/docs/fundamentals/api/how-to/create-via-api.mdx

@@ -24,7 +24,7 @@ Cloudflare also recommends limiting the use of the token via client IP address f
 
 ## Creating API tokens with the API
 
-You can create a user owned token or account owned token to use with the API. Refer to the [user owned token](/api/resources/user/subresources/tokens/methods/create/) or the [account owned token](/api/resources/accounts/subresources/tokens/methods/create/) API schema docs for more information. 
+You can create a user owned token or account owned token to use with the API. Refer to the [user owned token](/api/resources/user/subresources/tokens/methods/create/) or the [account owned token](/api/resources/accounts/subresources/tokens/methods/create/) API schema docs for more information.
 
 To create a token:
 
@@ -75,7 +75,7 @@ API token policies support three resource types: `User`, `Account`, and `Zone`.
 :::note
 
 
-Fetch each object's ID by calling the appropriate `GET <object>` API. Refer to [User](/api/resources/user/methods/get/), [Account](/api/resources/accounts/methods/list/), and [Zone](/api/resources/zones/methods/list/) documentation for more details. 
+Fetch each object's ID by calling the appropriate `GET <object>` API. Refer to [User](/api/resources/user/methods/get/), [Account](/api/resources/accounts/methods/list/), and [Zone](/api/resources/zones/methods/list/) documentation for more details.
 :::
 
 ##### Account

src/content/docs/fundamentals/api/troubleshooting.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 5
 head:
   - tag: title
-    content: Troubleshooting | Cloudflare API 
+    content: Troubleshooting | Cloudflare API
 ---
 
 ## The token is not verified

src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx

@@ -27,7 +27,7 @@ When you onboard your website or application to Cloudflare, Cloudflare becomes t
 Cloudflare only becomes the primary authoritative DNS provider when you use the default, full DNS setup. For alternative options, refer to [DNS setups](/dns/zone-setups/).
 :::
 
-If your [domain's status](/dns/zone-setups/reference/domain-status/) is active and the queried DNS record is set to `proxied`, Cloudflare responds with an [anycast IP address](/fundamentals/concepts/cloudflare-ip-addresses/), instead of the origin IP address defined in your DNS table. 
+If your [domain's status](/dns/zone-setups/reference/domain-status/) is active and the queried DNS record is set to `proxied`, Cloudflare responds with an [anycast IP address](/fundamentals/concepts/cloudflare-ip-addresses/), instead of the origin IP address defined in your DNS table.
 
 Your domain status is active when your [nameservers are updated](/dns/nameservers/update-nameservers/) to point to Cloudflare and have been authenticated. The [proxy status](/dns/proxy-status/) defines how Cloudflare treats queries for specific DNS records. The [anycast IP address](/fundamentals/concepts/cloudflare-ip-addresses/) is used to distribute traffic amongst Cloudflare's network, which protects your website or app from [DDoS](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) and other attacks, while optimizing site speed.
 

src/content/docs/fundamentals/reference/policies-compliances/cloudflare-cookies.mdx

@@ -46,7 +46,7 @@ Bot Management is available to Enterprise customers as an add-on service. Contac
 
 ### cf_clearance cookie for Cloudflare bot products
 
-The `cf_clearance` cookie is required for [JavaScript detections](/bots/reference/javascript-detections/). JavaScript detections are stored in the `cf_clearance` cookie. 
+The `cf_clearance` cookie is required for [JavaScript detections](/bots/reference/javascript-detections/). JavaScript detections are stored in the `cf_clearance` cookie.
 
 ### cf\_ob\_info and cf\_use\_ob cookie for Cloudflare Always Online
 

src/content/docs/fundamentals/reference/policies-compliances/compliance-docs.mdx

@@ -15,7 +15,7 @@ To access compliance documentation:
 
 :::note
 
-For confidentiality purposes, only **Super Administrators** for an account can access compliance documentation. 
+For confidentiality purposes, only **Super Administrators** for an account can access compliance documentation.
 :::
 
 ## Tax documentation

src/content/docs/fundamentals/reference/sdk-ecosystem-support-policy.mdx

@@ -14,7 +14,7 @@ We provide three primary stages of development: early access, active support, an
 
 :::note
 
-These lifecycle stages may be referred to in different terms across Cloudflare products, but the underlying principles are the same. 
+These lifecycle stages may be referred to in different terms across Cloudflare products, but the underlying principles are the same.
 :::
 
 ### Early access
@@ -47,7 +47,7 @@ The SDK ecosystem follows semantic versioning, which defines versions as follows
 
 As Cloudflare has recently swapped to [automatically generating our libraries using OpenAPI](https://blog.cloudflare.com/lessons-from-building-an-automated-sdk-pipeline), we have relaxed the strict versioning requirements on the libraries (Terraform is not changing). Minor releases *may* contain breaking changes in the forms of method, structure, or type renames as the service owners stabilize their schemas and iterate on usability improvements.
 
-If this is not suitable for your use case, pin to a known good version or use the previous major version of the library. 
+If this is not suitable for your use case, pin to a known good version or use the previous major version of the library.
 :::
 
 Depending on your needs, you should ensure your application's package manager versioning is configured correctly. At a minimum, restrict installation to the current major version of the library or tool you are using to prevent any major version upgrades occurring automatically.

src/content/docs/fundamentals/security/under-ddos-attack.mdx

@@ -20,5 +20,5 @@ Common signs that you are under DDoS attack include:
 
 :::note
 
-If you are currently under DDoS attack, refer to our guide on [responding to a DDoS attack](/ddos-protection/best-practices/respond-to-ddos-attacks/). 
+If you are currently under DDoS attack, refer to our guide on [responding to a DDoS attack](/ddos-protection/best-practices/respond-to-ddos-attacks/).
 :::