diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx index fdd3264b42cc13..7fb5428ebd440d 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-access-login-events.mdx @@ -8,7 +8,7 @@ In this example, we are going to use the GraphQL Analytics API to retrieve logs The following API call will request logs for a single Access login event and output the requested fields. The authentication request is identified by its **Ray ID**, which you can obtain from the `403` Forbidden page shown to the user. -You will need to insert your ``, your API credentials in ``[^1], and substitute your own values for the following variables: +You will need to insert your ``, your API credentials in ``[^1], and substitute your own values for the following variables: * `rayID`: A unique identifier assigned to the authentication request. * `datetimeStart`: The earliest event time to query (no earlier than September 16, 2022). @@ -103,4 +103,4 @@ Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/fe You can compare the query results to your Access policies to understand why a user was blocked. For example, if your application requires a valid mTLS certificate, Access blocked the request shown above because `mtlsStatus`, `mtlsCommonName`, and `mtlsCertSerialId` are empty. -[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. \ No newline at end of file +[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx index 9a9c75e6e4a08c..378c50d3b5e5f9 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx @@ -6,7 +6,7 @@ title: Querying Firewall Events with GraphQL In this example, we are going to use the GraphQL Analytics API to query for Firewall Events over a specified time period. -The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace ``, ``, and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace ``, ``, and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -183,4 +183,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. \ No newline at end of file +[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx index 00b8a116764462..1c94cc917c4daf 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx @@ -6,7 +6,7 @@ title: Querying Magic Firewall Intrusion Detection System (IDS) samples with Gra In this example, we are going to use the GraphQL Analytics API to query for IDS samples over a specified time period. -The following API call will request IDS samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your account tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request IDS samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your account tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -102,4 +102,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. \ No newline at end of file +[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx index 598181b891a80c..e70c6025917fb2 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx @@ -6,7 +6,7 @@ title: Querying Magic Firewall Samples with GraphQL In this example, we are going to use the GraphQL Analytics API to query for Magic Firewall Samples over a specified time period. -The following API call will request Magic Firewall Samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request Magic Firewall Samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -107,4 +107,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. \ No newline at end of file +[^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. diff --git a/src/content/docs/analytics/network-analytics/configure/displayed-data.mdx b/src/content/docs/analytics/network-analytics/configure/displayed-data.mdx index 253a06b964231b..19739ad7087671 100644 --- a/src/content/docs/analytics/network-analytics/configure/displayed-data.mdx +++ b/src/content/docs/analytics/network-analytics/configure/displayed-data.mdx @@ -55,7 +55,7 @@ To filter based on the type of data associated with one of the Network Analytics :::note -This feature is only available to Magic Transit and Magic WAN users. +This feature is only available to Magic Transit and Magic WAN users. ::: Select **Create Magic Firewall rule** to create a [Magic Firewall](/magic-firewall/) rule that will block all traffic matching the selected filters in Network Analytics. @@ -79,6 +79,6 @@ To filter for these traffic events: 3. Select **Add filter**. - Set `Verdict equals drop`. - Set `Action equals pass`. -4. Select **Apply**. +4. Select **Apply**. -By setting `verdict` to `drop` and `outcome` as `pass`, we are filtering for traffic that was marked as a detection (that is, verdict was `drop`) but was not dropped (for example, outcome was `pass`). \ No newline at end of file +By setting `verdict` to `drop` and `outcome` as `pass`, we are filtering for traffic that was marked as a detection (that is, verdict was `drop`) but was not dropped (for example, outcome was `pass`).