[Fundamentals] Move Trace request & update redirects (#19944)

dcpena · pedrosousa · web-flow · commit bc2253fcb9ad · 2025-02-13T10:37:40.000-06:00
* Move Trace request &amp; update redirects

* Add redirects

* Fix links and update partial (inputParameters &gt;&gt; params)

* Fix one last link

---------

Co-authored-by: Pedro Sousa &lt;680496+pedrosousa@users.noreply.github.com&gt;
diff --git a/public/_redirects b/public/_redirects
@@ -415,7 +415,7 @@
 /email-security/setup/api-deployment/office365-api/ /email-security/setup/post-delivery-deployment/api/office365-api/ 301
 /email-security/email-configuration/retract-settings/gmail-retraction/ /email-security/deployment/api/setup/gsuite-bcc-setup/add-retraction/ 301
 /cloudflare-one/insights/email-monitoring/email-security-logs/ /cloudflare-one/insights/email-monitoring/enable-logs/ 301
-/cloudflare-one/insights/email-monitoring/phishing-report/ /cloudflare-one/insights/email-monitoring/download-disposition-report/ 301 
+/cloudflare-one/insights/email-monitoring/phishing-report/ /cloudflare-one/insights/email-monitoring/download-disposition-report/ 301
 
 
 # firewall
@@ -614,10 +614,14 @@
 /fundamentals/basic-tasks/prevent-ddos-attacks-external/ /fundamentals/security/prevent-ddos-attacks-external/ 301
 /fundamentals/basic-tasks/protect-your-origin-server/ /fundamentals/security/protect-your-origin-server/ 301
 /fundamentals/basic-tasks/pci-scans/ /fundamentals/security/pci-scans/ 301
-/fundamentals/basic-tasks/trace-request/ /fundamentals/security/trace-request/ 301
-/fundamentals/basic-tasks/trace-request/how-to/ /fundamentals/security/trace-request/how-to/ 301
-/fundamentals/basic-tasks/trace-request/limitations/ /fundamentals/security/trace-request/limitations/ 301
-/fundamentals/basic-tasks/trace-request/changelog/ /fundamentals/security/trace-request/changelog/ 301
+/fundamentals/basic-tasks/trace-request/ /fundamentals/trace-request/ 301
+/fundamentals/basic-tasks/trace-request/how-to/ /fundamentals/trace-request/how-to/ 301
+/fundamentals/basic-tasks/trace-request/limitations/ /fundamentals/trace-request/limitations/ 301
+/fundamentals/basic-tasks/trace-request/changelog/ /fundamentals/trace-request/changelog/ 301
+/fundamentals/security/trace-request/ /fundamentals/trace-request/ 301
+/fundamentals/security/trace-request/how-to/ /fundamentals/trace-request/how-to/ 301
+/fundamentals/security/trace-request/limitations/ /fundamentals/trace-request/limitations/ 301
+/fundamentals/security/trace-request/changelog/ /fundamentals/trace-request/changelog/ 301
 
 # gateway
 /gateway/about/ /cloudflare-one/policies/gateway/ 301
diff --git a/src/content/changelogs-next/2025-01-09-rules-overview.mdx b/src/content/changelogs-next/2025-01-09-rules-overview.mdx
@@ -11,9 +11,10 @@ date: 2025-01-09T11:00:00Z
 ![Rules Overview Interface](~/assets/images/changelog-next/rules/rules-overview.gif)
 
 What you can do:
+
 - **See all your rules in one place** – No more clicking around.
 - **Find rules faster** – Search by name.
 - **Understand execution order** – See how rules run in sequence.
-- **Debug easily** – Use [Trace](/fundamentals/security/trace-request/) without switching tabs.
+- **Debug easily** – Use [Trace](/fundamentals/trace-request/) without switching tabs.
 
 Check it out in [Rules > Overview](https://dash.cloudflare.com/?to=/:account/:zone/rules/overview).
diff --git a/src/content/changelogs/trace.yaml b/src/content/changelogs/trace.yaml
@@ -1,7 +1,7 @@
 ---
-link: "/fundamentals/security/trace-request/changelog/"
+link: "/fundamentals/trace-request/changelog/"
 productName: Trace
-productLink: "/fundamentals/security/trace-request/"
+productLink: "/fundamentals/trace-request/"
 productArea: Core platform
 productAreaLink: /fundamentals/reference/changelog/platform/
 entries:
diff --git a/src/content/docs/cache/how-to/cache-rules/index.mdx b/src/content/docs/cache/how-to/cache-rules/index.mdx
@@ -30,5 +30,5 @@ The following table describes Cache Rules availability per plan.
 <Render
 	file="troubleshoot-rules-with-trace"
 	product="rules"
-	params={{ one: "Cache Rules" }}
+	params={{ rulesFeatureName: "Cache Rules" }}
 />
diff --git a/src/content/docs/fundamentals/performance/index.mdx b/src/content/docs/fundamentals/performance/index.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: navigation
 title: Performance
 sidebar:
-  order: 6
+  order: 5
   group:
     hideIndex: true
 
diff --git a/src/content/docs/fundamentals/trace-request/changelog.mdx b/src/content/docs/fundamentals/trace-request/changelog.mdx
diff --git a/src/content/docs/fundamentals/trace-request/how-to.mdx b/src/content/docs/fundamentals/trace-request/how-to.mdx
diff --git a/src/content/docs/fundamentals/trace-request/index.mdx b/src/content/docs/fundamentals/trace-request/index.mdx
@@ -2,6 +2,7 @@
 pcx_content_type: concept
 title: Trace a request
 sidebar:
+  order: 5
   badge:
     text: Beta
 head:
diff --git a/src/content/docs/fundamentals/trace-request/limitations.mdx b/src/content/docs/fundamentals/trace-request/limitations.mdx
diff --git a/src/content/docs/rules/compression-rules/index.mdx b/src/content/docs/rules/compression-rules/index.mdx
@@ -55,5 +55,5 @@ The following fields are commonly used in expressions of compression rules:
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "compression rules" }}
+	params={{ rulesFeatureName: "compression rules" }}
 />
diff --git a/src/content/docs/rules/configuration-rules/index.mdx b/src/content/docs/rules/configuration-rules/index.mdx
@@ -37,5 +37,5 @@ The number of available configuration rules varies according to your Cloudflare
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "configuration rules" }}
+	params={{ rulesFeatureName: "configuration rules" }}
 />
diff --git a/src/content/docs/rules/origin-rules/index.mdx b/src/content/docs/rules/origin-rules/index.mdx
@@ -50,4 +50,7 @@ If you override the hostname with an origin rule (via `Host` header override or
 
 Like [Page Rules](/rules/page-rules/), an origin rule performing a `Host` header override will update the SNI value of the original request to the same value of the `Host` header. To set an SNI value different from the `Host` header override, add an SNI override in the same origin rule or create a separate origin rule for this purpose.
 
-<Render file="troubleshoot-rules-with-trace" params={{ one: "origin rules" }} />
+<Render
+	file="troubleshoot-rules-with-trace"
+	params={{ rulesFeatureName: "origin rules" }}
+/>
diff --git a/src/content/docs/rules/reference/page-rules-migration.mdx b/src/content/docs/rules/reference/page-rules-migration.mdx
@@ -32,7 +32,7 @@ Improvements in modern Rules features include:
 
 - **New engine**: New Rules features are powered by the [Ruleset Engine](/ruleset-engine/), which offers versatile configuration with a robust language that supports many HTTP request and response fields.
 - **Improved scalability**: Thanks to the improved scalability, Cloudflare plans now have increased quotas.
-- **Easier troubleshooting**: Rule execution is more predictable, since each rule operates independently, simplifying troubleshooting. Additionally, [Cloudflare Trace](/fundamentals/security/trace-request/) helps understand rule interactions.
+- **Easier troubleshooting**: Rule execution is more predictable, since each rule operates independently, simplifying troubleshooting. Additionally, [Cloudflare Trace](/fundamentals/trace-request/) helps understand rule interactions.
 - **Improved consistency**: New Rules features also ensure consistency, with common fields and capabilities shared across products, offering a seamless experience and predictable Terraform configurations.
 
 ## Key differences
diff --git a/src/content/docs/rules/transform/index.mdx b/src/content/docs/rules/transform/index.mdx
@@ -74,5 +74,5 @@ Request and response fields are immutable within each [phase](/ruleset-engine/ab
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "Transform Rules" }}
+	params={{ rulesFeatureName: "Transform Rules" }}
 />
diff --git a/src/content/docs/rules/transform/request-header-modification/index.mdx b/src/content/docs/rules/transform/request-header-modification/index.mdx
@@ -67,5 +67,5 @@ You can create an HTTP request header modification rule [in the dashboard](/rule
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "HTTP request header modification rules" }}
+	params={{ rulesFeatureName: "HTTP request header modification rules" }}
 />
diff --git a/src/content/docs/rules/transform/response-header-modification/index.mdx b/src/content/docs/rules/transform/response-header-modification/index.mdx
@@ -75,5 +75,5 @@ You can create an HTTP response header modification rule [in the dashboard](/rul
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "HTTP response header modification rules" }}
+	params={{ rulesFeatureName: "HTTP response header modification rules" }}
 />
diff --git a/src/content/docs/rules/transform/troubleshooting.mdx b/src/content/docs/rules/transform/troubleshooting.mdx
@@ -6,7 +6,6 @@ sidebar:
 head:
   - tag: title
     content: Troubleshoot Transform Rules
-
 ---
 
 When troubleshooting a rule configuration, review the [Transform Rules evaluation](/rules/transform/#transform-rules-evaluation) section to understand how and when your Transform Rule is evaluated for each request.
@@ -17,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 modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/security/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
+To check if a request header modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original 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/rules/transform/url-rewrite/create-dashboard.mdx b/src/content/docs/rules/transform/url-rewrite/create-dashboard.mdx
@@ -70,6 +70,6 @@ Refer to [URL rewrite parameters](/rules/transform/url-rewrite/reference/paramet
 
 The **Request URL** value is only used to match the incoming request with a rule. It will not be used for capturing URL patterns for rewrites. If you are matching the URL path or query string in **Target path** or **Target query**, respectively, make sure that the **Request URL** pattern also matches the incoming request, or else the rule will not trigger.
 
-To validate rewrite URL rule matches, use [Cloudflare Trace](/fundamentals/security/trace-request/). To validate rewritten URLs, check your origin server.
+To validate rewrite URL rule matches, use [Cloudflare Trace](/fundamentals/trace-request/). To validate rewritten URLs, check your origin server.
 
 :::
diff --git a/src/content/docs/rules/transform/url-rewrite/index.mdx b/src/content/docs/rules/transform/url-rewrite/index.mdx
@@ -39,4 +39,7 @@ Create rewrite URL rules [in the dashboard](/rules/transform/url-rewrite/create-
 
 When using Cloudflare Images, you can use URL rewrites to serve images from a custom path. For more information, refer to [Serve images from custom domains](/images/manage-images/serve-images/serve-from-custom-domains/).
 
-<Render file="troubleshoot-rules-with-trace" params={{ one: "URL rewrites" }} />
+<Render
+	file="troubleshoot-rules-with-trace"
+	params={{ rulesFeatureName: "URL rewrites" }}
+/>
diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/faq.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/faq.mdx
@@ -6,17 +6,16 @@ sidebar:
 head:
   - tag: title
     content: FAQ — Bulk Redirects
-
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip } from "~/components";
 
 Below you will find answers to the most commonly asked questions regarding Bulk Redirects.
 
 To troubleshoot errors related to Bulk Redirects:
 
-* Refer to [Troubleshooting Cloudflare 10XXX Errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors/) for more information on runtime errors.
-* Use [Cloudflare Trace](/fundamentals/security/trace-request/) to determine if a rule is triggering for a specific URL.
+- Refer to [Troubleshooting Cloudflare 10XXX Errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors/) for more information on runtime errors.
+- Use [Cloudflare Trace](/fundamentals/trace-request/) to determine if a rule is triggering for a specific URL.
 
 ## What happens if the same source URL appears in two different Bulk Redirect Lists?
 
diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/index.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/index.mdx
@@ -25,4 +25,4 @@ Unlike dynamic URL redirects created in [Single Redirects](/rules/url-forwarding
 
 - [Availability](/rules/url-forwarding/#availability): Information on the Bulk Redirects quotas and features per Cloudflare plan.
 - [Execution order](/rules/url-forwarding/#execution-order): Execution order of the different Rules products.
-- [Trace a request](/fundamentals/security/trace-request/): Use Cloudflare Trace to determine if a bulk redirect rule is triggering for a specific URL.
+- [Trace a request](/fundamentals/trace-request/): Use Cloudflare Trace to determine if a bulk redirect rule is triggering for a specific URL.
diff --git a/src/content/docs/rules/url-forwarding/index.mdx b/src/content/docs/rules/url-forwarding/index.mdx
@@ -54,5 +54,5 @@ Single Redirects features and quotas are per zone and depend on the zone plan.
 
 <Render
 	file="troubleshoot-rules-with-trace"
-	params={{ one: "URL redirects" }}
+	params={{ rulesFeatureName: "URL redirects" }}
 />
diff --git a/src/content/docs/rules/url-forwarding/single-redirects/index.mdx b/src/content/docs/rules/url-forwarding/single-redirects/index.mdx
@@ -23,4 +23,4 @@ Single Redirects allow you to create static or dynamic URL <GlossaryTooltip term
 
 - [Availability](/rules/url-forwarding/#availability): Information on the Single Redirects quotas and features per Cloudflare plan.
 - [Execution order](/rules/url-forwarding/#execution-order): Execution order of the different Rules products.
-- [Trace a request](/fundamentals/security/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
+- [Trace a request](/fundamentals/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
diff --git a/src/content/partials/rules/troubleshoot-rules-with-trace.mdx b/src/content/partials/rules/troubleshoot-rules-with-trace.mdx
@@ -1,10 +1,10 @@
 ---
-inputParameters: rulesFeatureName
-
+params:
+  - rulesFeatureName
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
 ## Troubleshooting
 
-When troubleshooting {props.one}, use [Cloudflare Trace](/fundamentals/security/trace-request/) to determine if a rule is triggering for a specific URL.
+When troubleshooting {props.rulesFeatureName}, use [Cloudflare Trace](/fundamentals/trace-request/) to determine if a rule is triggering for a specific URL.
