Skip to content

Commit 09601c2

Browse files
consolidaded partials
1 parent 5cd08eb commit 09601c2

File tree

4 files changed

+64
-86
lines changed

4 files changed

+64
-86
lines changed

src/content/partials/networking-services/analytics/magic-tunnel-traffic-analytics.mdx

Lines changed: 0 additions & 27 deletions
This file was deleted.

src/content/partials/networking-services/analytics/network-analytics-data-averages.mdx

Lines changed: 0 additions & 5 deletions
This file was deleted.

src/content/partials/networking-services/analytics/network-analytics.mdx

Lines changed: 64 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ params:
33
- magicWord
44
---
55

6-
import { GlossaryTooltip, Markdown, Render } from "~/components"
6+
import { GlossaryTooltip, Markdown } from "~/components"
77

88
{ props.magicWord === "Magic Transit" && (
99
<>
@@ -23,18 +23,74 @@ import { GlossaryTooltip, Markdown, Render } from "~/components"
2323
</>
2424
)}
2525

26-
<Render file="analytics/network-analytics-data-averages" product="networking-services" />
26+
Data is aggregated over time intervals that vary based on your selected zoom level. For example, a daily view shows 24-hour averages, which can flatten out short-term traffic spikes. As a result, longer time intervals will display lower peak bandwidth values compared to more granular views like five-minute intervals.
2727

2828
Refer to [Network Analytics](/analytics/network-analytics/) documentation to learn more.
2929

3030
## Network traffic data filters
3131

32-
<Render
33-
file="analytics/network-traffic-filters"
34-
product="networking-services"
35-
params={{ magicWord: props.magicWord }}
36-
/>
32+
{ props.magicWord === "Magic Transit" && (
33+
<>
34+
<Markdown
35+
text={`
36+
Magic Transit customers can account for all traffic flows that ingresses Cloudflare's network, is blocked by DDoS rules or Magic Firewall, and egresses Cloudflare's network. This allows customers to track the total packets and bytes that traverse Cloudflare's network and are ultimately destined for their own network. This will also give Magic Transit customers increased visibility into any traffic flows that are unaccounted for.
37+
`}
38+
inline={false}
39+
/>
40+
</>
41+
)
42+
}
43+
44+
{ (props.magicWord === "Magic WAN" || props.magicWord === "WAN Tunnels") && (
45+
<>
46+
<Markdown
47+
text={`
48+
Magic WAN customers have increased visibility into the various traffic flows across Cloudflare One products including:
49+
50+
- Traffic ingressing to Cloudflare's network via WARP
51+
- Traffic egressing Cloudflare's network via WARP
52+
- Traffic egressing Cloudflare's network via Cloudflare Tunnel (cloudflared)
53+
54+
`}
55+
inline={false}
56+
/>
57+
</>
58+
)
59+
}
60+
61+
The complete list of filters includes:
62+
63+
- A list of your top tunnels by traffic volume.
64+
- Traffic source and destination for type of traffic, on-ramps and off-ramps, <GlossaryTooltip term="IP address">IP addresses</GlossaryTooltip>, and ports.
65+
- Destination IP ranges and ASNs.
66+
- Protocols and packet sizes.
67+
- Samples of all GRE or IPsec tunnel traffic entering or leaving Cloudflare's network.
68+
- Mitigations applied (such as DDoS and Magic Firewall) to traffic entering Cloudflare.
69+
70+
Refer below to [Access Magic Tunnel traffic analytics](#access-magic-tunnel-traffic-analytics) to learn how to access these filters.
3771

3872
## Access Magic Tunnel traffic analytics
3973

40-
<Render file="analytics/magic-tunnel-traffic-analytics" product="networking-services" />
74+
1. Go to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
75+
2. Select **Analytics & Logs** > **Network Analytics**.
76+
3. In the **All Traffic** tab, scroll to **Top Insights** to access network traffic filters. By default, the dashboard shows five items, but you can display up to 25 items at once. Select the drop-down menu to make your change.
77+
4. (Optional) Hover your mouse over one of the types of traffic. You can then choose to filter for that type of traffic, or exclude it from the results.
78+
5. You can also apply filters to adjust the scope of information displayed. Scroll to **All traffic** > **Add filter**.
79+
6. In the **New filter** popover, choose what type of data you want to display from the left dropdown menu, an operator from the middle dropdown menu, and an action from the right dropdown menu. For example:
80+
81+
```txt
82+
<DESTINATION_TUNNELS> | _equals_ | <NAME_OF_YOUR_TUNNEL>
83+
```
84+
85+
This lets you examine traffic from specific Source tunnels and/or Destination tunnels.
86+
87+
## Feature notes
88+
89+
- For Magic Transit customers, `Non-tunnel traffic` will often represent traffic from the public Internet or traffic via [CNIs](/network-interconnect/).
90+
- For Magic WAN / WAN tunnels customers, `Non-tunnel traffic` refers to traffic outside of GRE or IPsec tunnels. This can include traffic from:
91+
- [WARP](/cloudflare-one/team-and-resources/devices/warp/)
92+
- [CNIs](/network-interconnect/)
93+
- Traffic destined for the public Internet via [Gateway](/cloudflare-one/traffic-policies/)
94+
- Traffic destined for applications behind [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/)
95+
96+
The label `Non-Tunnel traffic` is a placeholder, and more specific labels will be applied to this category of traffic in the near future.

src/content/partials/networking-services/analytics/network-traffic-filters.mdx

Lines changed: 0 additions & 46 deletions
This file was deleted.

0 commit comments

Comments
 (0)