Network Analytics v1 to Network Analytics v2
In early 2020, Cloudflare released the first version of the Network Analytics dashboard and its corresponding API. The second version (Network Analytics v2) was made available on 2021-09-13.
Learn more about the concepts introduced in Network Analytics v2.
The following table compares the features of NAv1 and NAv2:
| Feature | NAv1 | NAv2 |
|---|---|---|
| Sampling rate | 1/8,192 packets | Varies between 1/100 and 1/1,000,000 packets, depending on the mitigation service. |
| Sampling method | Core Sample Enrichment | Edge Sample Enrichment |
| Historical data retention method | Aggregated roll-ups | Adaptive Bit Rate |
| Retention period | 1-min roll-ups: 30 days 1-hour roll-ups: 6 months 1-day roll-ups: 1 year Attack roll-ups: 1 year | All nodes: 16 weeks |
| Attack mitigation systems | dosd | dosd, flowtrackd*, and Magic Firewall* |
| Examples of new fields | n/a | Rule ID GRE tunnel ID Packet size |
* Applicable only for Magic Transit customers.
For more information on the differences in terms of sampling method and historical data retention, refer to Main differences between Network Analytics v1 and v2.
NAv2 uses the same API endpoint but makes use of new nodes. While NAv1 has three nodes for aggregated roll-ups for all traffic and attacks, and one node for attacks, NAv2 has one node for all traffic and attacks, and four separate nodes for attacks that vary based on the mitigation system.
| Node type | NAv1 | NAv2 for Magic Transit | NAv2 for Spectrum |
|---|---|---|---|
| Main node(s) | ipFlows1mGroupsipFlows1hGroupsipFlows1dGroups | magicTransitNetworkAnalyticsAdaptiveGroups | spectrumNetworkAnalyticsAdaptiveGroups |
| Attack node(s) | ipFlows1mAttacksGroups | dosdNetworkAnalyticsAdaptiveGroupsdosdAttackAnalyticsGroupsflowtrackdNetworkAnalyticsAdaptiveGroupsmagicFirewallNetworkAnalyticsAdaptiveGroups | dosdNetworkAnalyticsAdaptiveGroupsdosdAttackAnalyticsGroups |
Each row represents one packet sample. The data is sampled at Cloudflare’s edge at various rates. You can also query the sample rate from the nodes using the sample_interval field.
For reference information on NAv2 nodes, refer to the NAv2 node reference.
Refer to NAv1 to NAv2 schema map for a mapping of schema fields from NAv1 nodes to NAv2 nodes. Follow this recommended mapping when migrating to NAv2.
The following example queries the top 20 logs of traffic dropped by mitigation systems different from Magic Firewall within a given time range, ordered by destination IP address.
{ viewer { accounts(filter: {accountTag: "<REDACTED>"}) { magicTransitNetworkAnalyticsAdaptiveGroups( filter: { datetime_gt: "2021-10-01T00:00:00Z", datetime_lt: "2021-10-05T00:00:00Z", outcome_like: "drop", mitigationSystem_neq: "magic-firewall" }, limit: 20, orderBy: [ipDestinationAddress_ASC]) { dimensions { outcome mitigationSystem ipSourceAddress ipDestinationAddress ipProtocol destinationPort } } } }}The mitigationSystem field can take one the following values:
dosdfor DDoS managed rulesets (Network-layer DDoS Attack Protection or HTTP DDoS Attack Protection).flowtrackdfor Advanced TCP Protection.magic-firewallfor Magic Firewall.- Empty string for unmitigated traffic.