added content

Author: marciocloudflare

src/content/partials/magic-transit/tunnels-reference/tunnels-encapsulation.mdx

@@ -6,7 +6,7 @@ params:
   - tunnelEndpoints
 ---
 
-import { GlossaryTooltip, Markdown, Details } from "~/components";
+import { AnchorHeading, GlossaryTooltip, Markdown, Details } from "~/components";
 
 ## Tunnels and encapsulation
 
@@ -215,3 +215,12 @@ Additionally, the IKE ID type of `ID_IPV4_ADDR` is supported if the following tw
 :::caution
 Make sure each IPsec tunnel has a unique combination of a <a href={props.tunnelEndpoints}>Cloudflare endpoint and customer endpoint</a>. If this combination is not unique among your IPsec tunnels, you should use one of the custom IKE formats (`ID_RFC822_ADDR`, `ID_FQDN`, or `ID_KEY_ID`) to specify the tunnel ID and account ID. This helps Cloudflare link the IKE packet to the right IPsec tunnel for tasks like authentication.
 :::
+
+{ props.magicWord === "Magic Transit" && (
+  <>
+	<AnchorHeading title="Network Analytics" depth={2} />
+	<p>Cloudflare's Network Analytics provides near real-time visibility into network and transport layer traffic patterns and DDoS attacks which can help troubleshoot IP traffic issues. You can also use Network Analytics to view information about the traffic that leaves Cloudflare's global network by reviewing ingress and egress tunnel traffic over a specific amount of time.</p>
+	<p>For more information, refer to [Analytics](/magic-transit/analytics/).</p>
+  </>
+  )
+}