From f8c30cbb912dd2998fde74a9ddcc206138484718 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 21 Apr 2025 16:13:23 +0100 Subject: [PATCH 1/4] Add sections for Analytics vs Logs and add info for GraphQL --- .../docs/dns/dns-firewall/analytics.mdx | 23 +++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx index 1a6fc2b98b08bee..5be05015610d094 100644 --- a/src/content/docs/dns/dns-firewall/analytics.mdx +++ b/src/content/docs/dns/dns-firewall/analytics.mdx @@ -1,16 +1,31 @@ --- 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/). +Consider the sections below to learn how to access analytics and logs for your DNS Firewall. -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. +## Analytics -## Response reasons +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. + +:::note +GraphQL replaces the [Cloudflare API endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/methods/get/) for DNS Firewall Analytics. +::: + +## 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. From e72d27e86d770451812df1d407f5f6ee2de0f2e9 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 24 Apr 2025 10:32:31 +0100 Subject: [PATCH 2/4] Adjust messaging around API (legacy) option --- src/content/docs/dns/dns-firewall/analytics.mdx | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx index 5be05015610d094..d5a3b1c0702ce1a 100644 --- a/src/content/docs/dns/dns-firewall/analytics.mdx +++ b/src/content/docs/dns/dns-firewall/analytics.mdx @@ -6,10 +6,14 @@ sidebar: --- +import { Badge } from "~/components"; + Consider the sections below to learn how to access analytics and logs for your DNS Firewall. ## 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/): @@ -17,9 +21,10 @@ The DNS Firewall analytics has two [schemas](/analytics/graphql-api/getting-star * `dnsFirewallAnalyticsAdaptive`: Retrieve information about individual DNS Firewall queries. * `dnsFirewallAnalyticsAdaptiveGroups`: Get reports on aggregate information only. -:::note -GraphQL replaces the [Cloudflare API endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/methods/get/) for DNS Firewall Analytics. -::: +### Cloudflare API + +You can also use the DNS Firewall API [reports endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/). + ## Logs From 41f048ca793db65e6de2d8b8acf1c356ff04cbef Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 24 Apr 2025 10:44:18 +0100 Subject: [PATCH 3/4] Attempt to use APIRequest component --- src/content/docs/dns/dns-firewall/analytics.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx index d5a3b1c0702ce1a..9859efc29c29a70 100644 --- a/src/content/docs/dns/dns-firewall/analytics.mdx +++ b/src/content/docs/dns/dns-firewall/analytics.mdx @@ -6,7 +6,7 @@ sidebar: --- -import { Badge } from "~/components"; +import { Badge, APIRequest } from "~/components"; Consider the sections below to learn how to access analytics and logs for your DNS Firewall. @@ -25,6 +25,13 @@ The DNS Firewall analytics has two [schemas](/analytics/graphql-api/getting-star You can also use the DNS Firewall API [reports endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/). + ## Logs From 6d2033b2483afe71693500288e704d325fd4bb1e Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 24 Apr 2025 10:44:40 +0100 Subject: [PATCH 4/4] Revert "Attempt to use APIRequest component" This reverts commit 41f048ca793db65e6de2d8b8acf1c356ff04cbef. --- src/content/docs/dns/dns-firewall/analytics.mdx | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/src/content/docs/dns/dns-firewall/analytics.mdx b/src/content/docs/dns/dns-firewall/analytics.mdx index 9859efc29c29a70..d5a3b1c0702ce1a 100644 --- a/src/content/docs/dns/dns-firewall/analytics.mdx +++ b/src/content/docs/dns/dns-firewall/analytics.mdx @@ -6,7 +6,7 @@ sidebar: --- -import { Badge, APIRequest } from "~/components"; +import { Badge } from "~/components"; Consider the sections below to learn how to access analytics and logs for your DNS Firewall. @@ -25,13 +25,6 @@ The DNS Firewall analytics has two [schemas](/analytics/graphql-api/getting-star You can also use the DNS Firewall API [reports endpoint](/api/resources/dns_firewall/subresources/analytics/subresources/reports/). - ## Logs