diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx
index 1a6fc2b98b08bee..d5a3b1c0702ce1a 100644
--- a/src/content/docs/dns/dns-firewall/analytics.mdx
+++ b/src/content/docs/dns/dns-firewall/analytics.mdx
@@ -1,16 +1,36 @@
 ---
 pcx_content_type: navigation
-title: Analytics
+title: Analytics and logs
 sidebar:
   order: 3
 
 ---
 
-To access analytics for your DNS Firewall, use the [Cloudflare API](/api/resources/dns_firewall/subresources/analytics/subresources/reports/methods/get/).
+import { Badge } from "~/components";
 
-Alternatively, [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.
+Consider the sections below to learn how to access analytics and logs for your DNS Firewall.
 
-## Response reasons
+## Analytics
+
+### GraphQL
+
+Use the [GraphQL API](/analytics/graphql-api/) to access DNS Firewall analytics. Refer to the GraphQL Analytics API documentation for guidance on how to [get started](/analytics/graphql-api/getting-started/).
+
+The DNS Firewall analytics has two [schemas](/analytics/graphql-api/getting-started/querying-basics/):
+
+* `dnsFirewallAnalyticsAdaptive`: Retrieve information about individual DNS Firewall queries.
+* `dnsFirewallAnalyticsAdaptiveGroups`: Get reports on aggregate information only.
+
+### Cloudflare API <Badge text="Legacy" variant="caution" size="medium" />
+
+You can also use the DNS Firewall API [reports endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/).
+
+
+## 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.
+
+### Response reasons
 
 When analyzing why Cloudflare DNS Firewall responded in one way or another to a specific query, consider the `responseReason` log field.