-
Notifications
You must be signed in to change notification settings - Fork 10k
Fix flowtrackd naming in schema map #23007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
646f25d
bec4aa4
dd17416
1f2e774
ed1a632
d5eb21c
a35bc09
c8fbcd1
e619a3d
67bf019
eccf318
f2cbfde
7f5cd29
891cd36
ee6800f
ccda82b
70b16fe
7f899c5
18ded1d
3d4fc69
fffbc86
05d4fb5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,7 +19,7 @@ The following table lists direct mappings between NAv1 and NAv2 fields, when ava | |
| </th> | ||
| <th>dosdNetworkAnalytics-AdaptiveGroups</th> | ||
| <th>dosdAttackAnalytics-Groups</th> | ||
| <th>flowtrackdNetworkAnalytics-AdaptiveGroups</th> | ||
| <th>flowtrackedNetworkAnalytics-AdaptiveGroups</th> | ||
| <th>magicFirewallNetworkAnalytics-AdaptiveGroups</th> | ||
| </tr> | ||
| </thead> | ||
|
|
@@ -320,7 +320,7 @@ The following table lists direct mappings between NAv1 and NAv2 fields, when ava | |
| </th> | ||
| <th>dosdNetworkAnalytics-AdaptiveGroups</th> | ||
| <th>dosdAttackAnalytics-Groups</th> | ||
| <th>flowtrackdNetworkAnalytics-AdaptiveGroups</th> | ||
| <code>flowtrackedNetworkAnalytics-AdaptiveGroups</code> | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This change not only modifies the name from 'flowtrackd' to 'flowtracked' (which may be incorrect), but also changes the HTML structure from a table header to a |
||
| <th>magicFirewallNetworkAnalytics-AdaptiveGroups</th> | ||
| </tr> | ||
| <tr> | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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 `<CLOUDFLARE_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^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 `<Cloudflare_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch fixing the parameter name from |
||
|
|
||
| ## 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. | ||
| [^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch updating the GitHub repository URL from 'llooker' to 'looker'. This ensures users are directed to the official Looker organization repository.