diff --git a/public/__redirects b/public/__redirects
index aea67698634845f..efabc0ced7a3f3a 100644
--- a/public/__redirects
+++ b/public/__redirects
@@ -957,7 +957,6 @@
/logs/log-fields/ /logs/reference/log-fields/ 301
/logs/logpull-api/ /logs/logpull/ 301
/logs/logpull-api/requesting-logs/ /logs/logpull/requesting-logs/ 301
-/logs/logpush/ /logs/about/ 301
/logs/logpush/aws-s3/ /logs/get-started/enable-destinations/aws-s3/ 301
/logs/logpush/azure/ /logs/get-started/enable-destinations/azure/ 301
/logs/logpush/google-cloud-storage/ /logs/get-started/enable-destinations/google-cloud-storage/ 301
@@ -971,6 +970,7 @@
/logs/reference/logpush-api-configuration/examples/example-logpush-curl/ /logs/tutorials/examples/example-logpush-curl/ 301
/logs/log-explorer/ /log-explorer/log-search/ 301
/logs/reference/glossary/ /logs/glossary/ 301
+/logs/about/ /logs/logpush/ 301
# magic-firewall
/magic-firewall/reference/examples/ /magic-firewall/how-to/add-rules/ 301
diff --git a/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx b/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
index 05a1293716d308a..478108da76517b0 100644
--- a/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
+++ b/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
@@ -8,6 +8,6 @@ date: 2025-01-15
Only available on Enterprise plans.
:::
-Cloudflare now allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/about/), including third-party destinations. Once exported, analyze and audit the data as best fits your organization! For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
+Cloudflare now allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. Once exported, analyze and audit the data as best fits your organization! For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
To set up a Logpush job, refer to [Logpush integration](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
index 6025a55e25b493c..d4bb34672e46f3b 100644
--- a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
+++ b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
@@ -121,4 +121,4 @@ This panel features metrics for Cloudflare Workers. To learn more, read [Cloudfl
### Logs
-The Logs tab is not a metrics feature. Instead, Customers in the Enterprise plan can enable the [Cloudflare Logs Logpush](/logs/about/) service. You can use Logpush to download and analyze data using any analytics tool of your choice.
+The Logs tab is not a metrics feature. Instead, Customers in the Enterprise plan can enable the [Cloudflare Logs Logpush](/logs/logpush/) service. You can use Logpush to download and analyze data using any analytics tool of your choice.
diff --git a/src/content/docs/analytics/analytics-integrations/graylog.mdx b/src/content/docs/analytics/analytics-integrations/graylog.mdx
index 7601eebed451396..2084eb72da51cf9 100644
--- a/src/content/docs/analytics/analytics-integrations/graylog.mdx
+++ b/src/content/docs/analytics/analytics-integrations/graylog.mdx
@@ -20,7 +20,7 @@ Before sending your Cloudflare log data to Graylog, make sure that you:
* Have an existing Graylog installation. Both single-node and cluster configurations are supported
* Have a Cloudflare Enterprise account with Cloudflare Logs enabled
-* Configure [Logpush](/logs/about/)
+* Configure [Logpush](/logs/logpush/)
:::note[Note]
@@ -34,7 +34,7 @@ Cloudflare logs are HTTP/HTTPS request logs in JSON format and are gathered from
Before getting Cloudflare logs into Graylog:
-1. Configure Cloudflare [Logpush](/logs/about/) to push logs with all desired fields to an AWS S3 bucket of your choice.
+1. Configure Cloudflare [Logpush](/logs/logpush/) to push logs with all desired fields to an AWS S3 bucket of your choice.
2. Download the latest [Graylog Integration for Cloudflare](https://github.com/Graylog2/graylog-s3-lambda/blob/master/content-packs/cloudflare/cloudflare-logpush-content-pack.json).
3. Decompress the zip file.
diff --git a/src/content/docs/analytics/analytics-integrations/looker.mdx b/src/content/docs/analytics/analytics-integrations/looker.mdx
index f7ad355d822f2fd..495ce03e479bf2a 100644
--- a/src/content/docs/analytics/analytics-integrations/looker.mdx
+++ b/src/content/docs/analytics/analytics-integrations/looker.mdx
@@ -19,7 +19,7 @@ Before sending your Cloudflare log data to Looker, make sure that you:
- Have an existing Looker account
- Have a Cloudflare Enterprise account with Cloudflare Logs enabled
-- Configure [Logpush](/logs/about/) or [Logpull](/logs/logpull/)
+- Configure [Logpush](/logs/logpush/) or [Logpull](/logs/logpull/)
- Load your data in a [database supported by Looker](https://looker.com/solutions/other-databases)
:::note[Note]
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
index f0fb9e6c1fe3c48..f1724ff3f04e0d2 100644
--- a/src/content/docs/analytics/network-analytics/index.mdx
+++ b/src/content/docs/analytics/network-analytics/index.mdx
@@ -26,6 +26,6 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
## Related resources
* [Cloudflare GraphQL API](/analytics/graphql-api/)
-* [Cloudflare Logpush](/logs/about/)
+* [Cloudflare Logpush](/logs/logpush/)
* [Migrating from Network Analytics v1 to Network Analytics v2](/analytics/graphql-api/migration-guides/network-analytics-v2/)
* [Cloudflare Network Analytics v1](/analytics/network-analytics/reference/network-analytics-v1/)
diff --git a/src/content/docs/bots/concepts/bot-tags.mdx b/src/content/docs/bots/concepts/bot-tags.mdx
index 2fa5f1533a572d1..7a318a78d5b907d 100644
--- a/src/content/docs/bots/concepts/bot-tags.mdx
+++ b/src/content/docs/bots/concepts/bot-tags.mdx
@@ -26,7 +26,7 @@ Once you [enable bot tags](#enable-bot-tags), you can see more information about
## Enable bot tags
-To enable bot tags, include the `BotTags` log field when using our [Logpush service](/logs/about/).
+To enable bot tags, include the `BotTags` log field when using our [Logpush service](/logs/logpush/).
## Limitations
diff --git a/src/content/docs/bots/frequently-asked-questions.mdx b/src/content/docs/bots/frequently-asked-questions.mdx
index 0ea4c00650dc6fc..f0874077461883e 100644
--- a/src/content/docs/bots/frequently-asked-questions.mdx
+++ b/src/content/docs/bots/frequently-asked-questions.mdx
@@ -63,7 +63,7 @@ You may also see Managed Challenge due to a triggered [WAF custom rule](/cloudfl
This does not mean that your traffic was blocked. It is the challenge sent to your user to determine whether they are likely human or likely bot.
-To understand if the result of the challenge was a success or a failure, you can verify using [Logpush](/logs/about/).
+To understand if the result of the challenge was a success or a failure, you can verify using [Logpush](/logs/logpush/).
### Does the WAF run before Super Bot Fight Mode?
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
index 60a793ba2336a37..d12ed5bc01bbc6e 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx
@@ -44,7 +44,7 @@ Build custom dashboards to share this information by specifying an individual cu
## Logpush
-[Logpush](/logs/about/) sends metadata from Cloudflare products to your cloud storage destination or SIEM.
+[Logpush](/logs/logpush/) sends metadata from Cloudflare products to your cloud storage destination or SIEM.
Using [filters](/logs/reference/filters/), you can send set sample rates (or not include logs altogether) based on filter criteria. This flexibility allows you to maintain selective logs for custom hostnames without massively increasing your log volume.
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
index 6d170d72a165769..82956d5d75bc4a0 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
@@ -149,7 +149,7 @@ To manually retrieve logs:
Only available on Enterprise plans.
:::
-Cloudflare allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/about/), including third-party destinations. For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
+Cloudflare allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
To set up the Logpush job, refer to [Logpush integration](/cloudflare-one/insights/logs/logpush/).
diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush.mdx
index 6920418c7d75199..8d364502034815f 100644
--- a/src/content/docs/cloudflare-one/insights/logs/logpush.mdx
+++ b/src/content/docs/cloudflare-one/insights/logs/logpush.mdx
@@ -9,7 +9,7 @@ sidebar:
Only available on Enterprise plans.
:::
-With Cloudflare's [Logpush](/logs/about/) service, you can configure the automatic export of Zero Trust logs to third-party storage destinations or to security information and event management (SIEM) tools. Once exported, your team can analyze and audit the data as needed.
+With Cloudflare's [Logpush](/logs/logpush/) service, you can configure the automatic export of Zero Trust logs to third-party storage destinations or to security information and event management (SIEM) tools. Once exported, your team can analyze and audit the data as needed.
## Export Zero Trust logs with Logpush
diff --git a/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx b/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx
index e4565f837f631b3..0261d6dec556961 100644
--- a/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx
+++ b/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx
@@ -75,7 +75,7 @@ Based on your report, DLP's machine learning will adjust its confidence in futur
Only available on Enterprise plans.
:::
-Gateway allows you to send copies of entire HTTP requests matched in HTTP Allow and Block policies to storage destinations configured in [Logpush](/logs/about/), including third-party destinations.
+Gateway allows you to send copies of entire HTTP requests matched in HTTP Allow and Block policies to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations.
To set up the DLP Forensic Copy Logpush job:
diff --git a/src/content/docs/containers/faq.mdx b/src/content/docs/containers/faq.mdx
index 81f2ecfb2220334..6b7440888eb87cc 100644
--- a/src/content/docs/containers/faq.mdx
+++ b/src/content/docs/containers/faq.mdx
@@ -33,7 +33,7 @@ retained for 3 days on Free plans and 7 days on Paid plans.
See [Workers Logs Pricing](/workers/observability/logs/workers-logs/#pricing) for details on cost.
-If you are an Enterprise user, you are able to export container logs via [Logpush](/logs/about)
+If you are an Enterprise user, you are able to export container logs via [Logpush](/logs/logpush/)
to your preferred destination.
## How are container instance locations selected?
diff --git a/src/content/docs/data-localization/limitations.mdx b/src/content/docs/data-localization/limitations.mdx
index 6d6698537a245df..832cccc64531540 100644
--- a/src/content/docs/data-localization/limitations.mdx
+++ b/src/content/docs/data-localization/limitations.mdx
@@ -44,7 +44,7 @@ Regional Services does not apply to [Subrequests](/workers/platform/limits/#subr
There are certain limitations and caveats when using Customer Metadata Boundary.
-Specifically most of the Zone Analytics & Logs UI Tabs will be showing up as empty, when configuring Customer Metadata Boundary to EU only. It is recommended to use the UI [Security Analytics](/waf/analytics/security-analytics/) instead, or the [HTTP request](/logs/reference/log-fields/zone/http_requests/) logs via [Logpush](/logs/about/).
+Specifically most of the Zone Analytics & Logs UI Tabs will be showing up as empty, when configuring Customer Metadata Boundary to EU only. It is recommended to use the UI [Security Analytics](/waf/analytics/security-analytics/) instead, or the [HTTP request](/logs/reference/log-fields/zone/http_requests/) logs via [Logpush](/logs/logpush/).
To configure Customer Metadata Boundary to EU only, you must disable Log Retention for all zones within your account. Log Retention is a legacy feature of [Logpull](/logs/logpull/).
diff --git a/src/content/docs/data-localization/metadata-boundary/index.mdx b/src/content/docs/data-localization/metadata-boundary/index.mdx
index cedff72ce954984..2d8c97ac9e93578 100644
--- a/src/content/docs/data-localization/metadata-boundary/index.mdx
+++ b/src/content/docs/data-localization/metadata-boundary/index.mdx
@@ -35,7 +35,7 @@ sequenceDiagram
## Log management
-Additionally, customers have the option to configure [Logpush](/logs/about/) to push their Customer Logs to various storage services, SIEMs, and log management providers.
+Additionally, customers have the option to configure [Logpush](/logs/logpush/) to push their Customer Logs to various storage services, SIEMs, and log management providers.
## Product specific-behavior
diff --git a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx b/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx
index b70128e959e5d7a..e86e253c6cffe42 100644
--- a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx
+++ b/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx
@@ -96,7 +96,7 @@ To view traffic flagged by L3/4 Adaptive DDoS Protection rules:
-You may also obtain information about flagged traffic through [Logpush](/logs/about/) or the [GraphQL API](/analytics/graphql-api/).
+You may also obtain information about flagged traffic through [Logpush](/logs/logpush/) or the [GraphQL API](/analytics/graphql-api/).
To determine if an adaptive rule fits your traffic in a way that will only mitigate attack traffic and will not cause false positives, review the traffic that is _Logged_ by the adaptive rules.
diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx
index d5a3b1c0702ce1a..5c715ff3a88072a 100644
--- a/src/content/docs/dns/dns-firewall/analytics.mdx
+++ b/src/content/docs/dns/dns-firewall/analytics.mdx
@@ -28,7 +28,7 @@ You can also use the DNS Firewall API [reports endpoint](/api/resources/dns_fire
## Logs
-You can [set up Logpush](/logs/about/) to deliver [DNS Firewall logs](/logs/reference/log-fields/account/dns_firewall_logs/) to a storage service, SIEM, or log management provider.
+You can [set up Logpush](/logs/logpush/) to deliver [DNS Firewall logs](/logs/reference/log-fields/account/dns_firewall_logs/) to a storage service, SIEM, or log management provider.
### Response reasons
diff --git a/src/content/docs/fundamentals/account/account-security/review-audit-logs.mdx b/src/content/docs/fundamentals/account/account-security/review-audit-logs.mdx
index 9eaa6f2dbfb2733..ec770e783783e16 100644
--- a/src/content/docs/fundamentals/account/account-security/review-audit-logs.mdx
+++ b/src/content/docs/fundamentals/account/account-security/review-audit-logs.mdx
@@ -20,4 +20,4 @@ import { Render } from "~/components"
## Retention
-Audit Logs are retained for 18 months before being deleted. Enterprise customers can use [Logpush](/logs/about/) to store Audit Logs for longer periods of time.
+Audit Logs are retained for 18 months before being deleted. Enterprise customers can use [Logpush](/logs/logpush/) to store Audit Logs for longer periods of time.
diff --git a/src/content/docs/learning-paths/data-center-protection/post-prefix-fine-tuning.mdx b/src/content/docs/learning-paths/data-center-protection/post-prefix-fine-tuning.mdx
index 776fc8e78f83bb6..db8f46e33bcbdb6 100644
--- a/src/content/docs/learning-paths/data-center-protection/post-prefix-fine-tuning.mdx
+++ b/src/content/docs/learning-paths/data-center-protection/post-prefix-fine-tuning.mdx
@@ -39,6 +39,6 @@ Refer to Magic Firewall's [best practices](/magic-firewall/best-practices/) for
## Optional
-- Enable [Logpush](/logs/about/) to your Security Information and Event Management (SIEM).
+- Enable [Logpush](/logs/logpush/) to your Security Information and Event Management (SIEM).
- Enable Magic Firewall's [Intrusion Detection System (IDS)](/magic-firewall/about/ids/). Requires Logpush and is only available for accounts with [Advanced Magic Firewall](/magic-firewall/plans/#advanced-features).
- Use [Magic Network Monitoring](/magic-network-monitoring/) for visibility into traffic on your non-Magic Transit prefixes, using NetFlow or sFlow from your CPEs.
\ No newline at end of file
diff --git a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
index aa11670eeb04313..f551cbef5c89c63 100644
--- a/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
+++ b/src/content/docs/learning-paths/prevent-ddos-attacks/advanced/improve-analytics.mdx
@@ -20,7 +20,7 @@ If needed, you can [restore the original visitor's IP address](/support/troubles
## Cloudflare Logs
-Enterprise customers can set up [Logpush](/logs/about/) jobs to regularly send Cloudflare logs to the SIEM system of their choice.
+Enterprise customers can set up [Logpush](/logs/logpush/) jobs to regularly send Cloudflare logs to the SIEM system of their choice.
This data can help when looking at long-term DDoS attack trends or when you need custom visualizations.
diff --git a/src/content/docs/logs/logpull/index.mdx b/src/content/docs/logs/logpull/index.mdx
index a617ffbe0eef19d..b35224721ebb06e 100644
--- a/src/content/docs/logs/logpull/index.mdx
+++ b/src/content/docs/logs/logpull/index.mdx
@@ -13,7 +13,7 @@ Cloudflare Logpull is a REST API for consuming request logs over HTTP. These log
:::caution
-Logpull is considered a legacy feature and we recommend using [Logpush](/logs/about/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
+Logpull is considered a legacy feature and we recommend using [Logpush](/logs/logpush/) or [Logs Engine](/logs/r2-log-retrieval/) instead for better performance and functionality.
:::
diff --git a/src/content/docs/logs/logpull/understanding-the-basics.mdx b/src/content/docs/logs/logpull/understanding-the-basics.mdx
index f6350ad1e361474..41ade2c7d29bae3 100644
--- a/src/content/docs/logs/logpull/understanding-the-basics.mdx
+++ b/src/content/docs/logs/logpull/understanding-the-basics.mdx
@@ -54,4 +54,4 @@ The following is a sample log with default fields:
## Data retention period
-You can query for logs starting from 1 minute in the past (relative to the actual time that you make the query) and go back at least 3 days and up to 7 days. For longer durations, we recommend using [Logpush](/logs/about/).
+You can query for logs starting from 1 minute in the past (relative to the actual time that you make the query) and go back at least 3 days and up to 7 days. For longer durations, we recommend using [Logpush](/logs/logpush/).
diff --git a/src/content/docs/logs/about.mdx b/src/content/docs/logs/logpush/index.mdx
similarity index 100%
rename from src/content/docs/logs/about.mdx
rename to src/content/docs/logs/logpush/index.mdx
diff --git a/src/content/docs/page-shield/policies/violations.mdx b/src/content/docs/page-shield/policies/violations.mdx
index 5c34100628e05cf..b8b76a3aa95641f 100644
--- a/src/content/docs/page-shield/policies/violations.mdx
+++ b/src/content/docs/page-shield/policies/violations.mdx
@@ -15,7 +15,7 @@ Only available to Enterprise customers with a paid add-on.
Shortly after you configure policies (or content security rules), the Cloudflare dashboard will start displaying any violations of those policies. This information will be available for policies with any [action](/page-shield/policies/#policy-actions) (_Allow_ and _Log_).
-Information about policy violations is also available via [GraphQL API](/analytics/graphql-api/) and [Logpush](/logs/about/).
+Information about policy violations is also available via [GraphQL API](/analytics/graphql-api/) and [Logpush](/logs/logpush/).
## Review policy violations in the dashboard
@@ -128,7 +128,7 @@ https://api.cloudflare.com/client/v4/graphql \
## Get policy violations via Logpush
-[Cloudflare Logpush](/logs/about/) supports pushing logs to storage services, SIEM systems, and log management providers.
+[Cloudflare Logpush](/logs/logpush/) supports pushing logs to storage services, SIEM systems, and log management providers.
Information about policy violations is available in the [`page_shield_events` dataset](/logs/reference/log-fields/zone/page_shield_events/).
diff --git a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
index 1b9317795bf8429..6006bd1e5204544 100644
--- a/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
+++ b/src/content/docs/reference-architecture/diagrams/serverless/fullstack-application.mdx
@@ -87,7 +87,7 @@ With [Workers AI](/workers-ai/), developers can run popular open-source models f
### 9. Cloudflare Observability
-Send logs from all services with [Logpush](/logs/about/), gather insights with [Workers Logs](/workers/observability/logs/) directly in the Cloudflare dashboard, collect custom metrics from Workers using [Workers Analytics Engine](/analytics/analytics-engine/), or observe and control AI applications with [AI Gateway](/ai-gateway/).
+Send logs from all services with [Logpush](/logs/logpush/), gather insights with [Workers Logs](/workers/observability/logs/) directly in the Cloudflare dashboard, collect custom metrics from Workers using [Workers Analytics Engine](/analytics/analytics-engine/), or observe and control AI applications with [AI Gateway](/ai-gateway/).
### 10. External Logs & Analytics
diff --git a/src/content/docs/rules/transform/troubleshooting.mdx b/src/content/docs/rules/transform/troubleshooting.mdx
index 618983e827ef7cf..a990f98f50b4ab9 100644
--- a/src/content/docs/rules/transform/troubleshooting.mdx
+++ b/src/content/docs/rules/transform/troubleshooting.mdx
@@ -16,6 +16,6 @@ For more information on runtime errors related to Transform Rules configuration,
Transform Rules performing request header modifications affect the HTTP headers sent by Cloudflare's network to your origin server. You will not find these headers in your browser request or response data, which can make it difficult to tell if the rule is working as intended.
-To check if a request header transform rule is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/rules/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original HTTP request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
+To check if a request header transform rule is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/rules/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/logpush/) only logs original HTTP request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
To add HTTP headers that website visitors will receive in their browsers, you must [modify the response headers](/rules/transform/response-header-modification/) instead.
diff --git a/src/content/docs/style-guide/how-we-docs/redirects.mdx b/src/content/docs/style-guide/how-we-docs/redirects.mdx
index dd80bf8fc0137db..fb1b75d2c4acefa 100644
--- a/src/content/docs/style-guide/how-we-docs/redirects.mdx
+++ b/src/content/docs/style-guide/how-we-docs/redirects.mdx
@@ -52,7 +52,7 @@ We have some automation to help [flag needed redirects](#potential-redirects).
Another time to add redirects is when you see a lot of `404` response codes on certain paths of your docs site. These `404` responses might be due to a missing redirect or mistyped link.
-We identify these status codes either through our [Cloudflare analytics](/analytics/account-and-zone-analytics/zone-analytics/) (ad hoc) or [Logpush job](/logs/about/) (more thorough, quarterly).
+We identify these status codes either through our [Cloudflare analytics](/analytics/account-and-zone-analytics/zone-analytics/) (ad hoc) or [Logpush job](/logs/logpush/) (more thorough, quarterly).
---
diff --git a/src/content/docs/waf/managed-rules/payload-logging/decrypt-in-logs.mdx b/src/content/docs/waf/managed-rules/payload-logging/decrypt-in-logs.mdx
index 4f5ac7151b96fd1..021f196fae740a5 100644
--- a/src/content/docs/waf/managed-rules/payload-logging/decrypt-in-logs.mdx
+++ b/src/content/docs/waf/managed-rules/payload-logging/decrypt-in-logs.mdx
@@ -7,7 +7,7 @@ sidebar:
import { GlossaryTooltip, RuleID } from "~/components";
-You can include the encrypted matched payload in your [Logpush](/logs/about/) jobs by adding the **General** > [**Metadata**](/logs/reference/log-fields/zone/firewall_events/#metadata) field from the Firewall Events dataset to your job.
+You can include the encrypted matched payload in your [Logpush](/logs/logpush/) jobs by adding the **General** > [**Metadata**](/logs/reference/log-fields/zone/firewall_events/#metadata) field from the Firewall Events dataset to your job.
The payload, in its encrypted form, is available in the [`encrypted_matched_data` property](#structure-of-encrypted_matched_data-property-in-logpush) of the `Metadata` field.
diff --git a/src/content/docs/waf/managed-rules/payload-logging/index.mdx b/src/content/docs/waf/managed-rules/payload-logging/index.mdx
index a15c19461c8838f..ab9b99f0703b3c0 100644
--- a/src/content/docs/waf/managed-rules/payload-logging/index.mdx
+++ b/src/content/docs/waf/managed-rules/payload-logging/index.mdx
@@ -38,7 +38,7 @@ To view the content of the payload in clear text, do one of the following:
- Decrypt the payload in the command line using the `matched-data-cli` tool. Refer to [Decrypt the payload content in the command line](/waf/managed-rules/payload-logging/command-line/decrypt-payload/) for details.
-- Decrypt the matched payload in your [Logpush](/logs/about/) job using a Worker before storing the logs in your SIEM system. Refer to [Store decrypted matched payloads in logs](/waf/managed-rules/payload-logging/decrypt-in-logs/) for details.
+- Decrypt the matched payload in your [Logpush](/logs/logpush/) job using a Worker before storing the logs in your SIEM system. Refer to [Store decrypted matched payloads in logs](/waf/managed-rules/payload-logging/decrypt-in-logs/) for details.
:::caution[Important]
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 346f3c27e6104e1..8c9534aede99792 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -11,7 +11,7 @@ sidebar:
import { WranglerConfig } from "~/components";
-[Cloudflare Logpush](/logs/about/) supports the ability to send [Workers Trace Event Logs](/logs/reference/log-fields/account/workers_trace_events/) to a [supported destination](/logs/get-started/enable-destinations/). Worker’s Trace Events Logpush includes metadata about requests and responses, unstructured `console.log()` messages and any uncaught exceptions. This product is available on the Workers Paid plan. For pricing information, refer to [Pricing](/workers/platform/pricing/#workers-trace-events-logpush).
+[Cloudflare Logpush](/logs/logpush/) supports the ability to send [Workers Trace Event Logs](/logs/reference/log-fields/account/workers_trace_events/) to a [supported destination](/logs/get-started/enable-destinations/). Worker’s Trace Events Logpush includes metadata about requests and responses, unstructured `console.log()` messages and any uncaught exceptions. This product is available on the Workers Paid plan. For pricing information, refer to [Pricing](/workers/platform/pricing/#workers-trace-events-logpush).
:::caution
diff --git a/src/content/partials/fundamentals/view-audit-log.mdx b/src/content/partials/fundamentals/view-audit-log.mdx
index 7be9f4bb800ea7f..0f2d6bc73967e0a 100644
--- a/src/content/partials/fundamentals/view-audit-log.mdx
+++ b/src/content/partials/fundamentals/view-audit-log.mdx
@@ -13,7 +13,7 @@ You can search these audit logs by user email or domain and filter by date range
:::note
-Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Log Push](/logs/about/) to make sure Audit Logs are always available and stored externally.
+Depending on the volume of data, the export of large amounts of events from Audit Logs might fail with errors. We always recommend using Cloudflare [Logpush](/logs/logpush/) to make sure Audit Logs are always available and stored externally.
:::
diff --git a/src/content/plans/index.json b/src/content/plans/index.json
index c5ac4aa607bc362..ee73b10c4cb8c61 100644
--- a/src/content/plans/index.json
+++ b/src/content/plans/index.json
@@ -90,7 +90,7 @@
},
"logpush": {
"title": "Logpush",
- "link": "/logs/about/",
+ "link": "/logs/logpush/",
"properties": {
"availability": {
"title": "Availability",