From ec4f60d2af8ebcf939ab17036fa3d28636fab726 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 8 May 2025 16:30:48 +0100 Subject: [PATCH 1/3] Create new anaytics page and fill in content --- src/content/docs/aegis/analytics.mdx | 30 ++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 src/content/docs/aegis/analytics.mdx diff --git a/src/content/docs/aegis/analytics.mdx b/src/content/docs/aegis/analytics.mdx new file mode 100644 index 00000000000000..eafe7ea14470e0 --- /dev/null +++ b/src/content/docs/aegis/analytics.mdx @@ -0,0 +1,30 @@ +--- +title: Analytics +pcx_content_type: reference +sidebar: + order: 7 +--- + +import { Type } from "~/components"; + +Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data on your Aegis IPs utilization, and monitor their capacity. As explained in [IPs allocation](/aegis/about/ips-allocation/), each Aegis IP can support 40,000 concurrent connections per origin IP. + +Refer to the GraphQL Analytics API documentation for guidance on how to [get started](/analytics/graphql-api/getting-started/). The specific Aegis schema is called `aegisIpUtilizationAdaptiveGroups`. + + +You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions: + +- `datetimeFiveMinutes` + - Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`. + +- `popName` + - The Cloudflare point of presence (PoP). For example, `sjc`. + +- `egressIp` + - Your assigned Aegis IP. For example, `192.0.2.1` + +- `origin` + - Origin IP and port. For example, `203.0.113.150:443`. + +- `popUtilizationKey` + - The Cloudflare point of presence (PoP), the Aegis IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443` From 680991543fb548ec4eece40678de7a997fe6334d Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 8 May 2025 16:51:58 +0100 Subject: [PATCH 2/3] Cross-link with ips-allocation and info on concurrent connections --- src/content/docs/aegis/about/ips-allocation.mdx | 2 ++ src/content/docs/aegis/analytics.mdx | 5 ++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/src/content/docs/aegis/about/ips-allocation.mdx b/src/content/docs/aegis/about/ips-allocation.mdx index 4b7b462eacb46e..03dc710e75924f 100644 --- a/src/content/docs/aegis/about/ips-allocation.mdx +++ b/src/content/docs/aegis/about/ips-allocation.mdx @@ -25,6 +25,8 @@ Refer to [connection forwarding](/aegis/about/connection-forwarding/) to underst Each Aegis IP can support 40,000 concurrent connections per origin IP. For example, if you have one Aegis IP and two origins (A and B), this single Aegis IP can support 40,000 concurrent connections to origin A, while simultaneously supporting 40,000 concurrent connections to origin B. +[GraphQL Analytics API](/aegis/analytics/) allows you to get visibility over Aegis IP utilization. + ## Regional services If you are using [Regional Services](/data-localization/regional-services/), you should take this into consideration when allocating Aegis IPv4. Traffic will egress from the specified locations as long as you have Aegis IPs provisioned in those locations. \ No newline at end of file diff --git a/src/content/docs/aegis/analytics.mdx b/src/content/docs/aegis/analytics.mdx index eafe7ea14470e0..40045bdd0dd9ce 100644 --- a/src/content/docs/aegis/analytics.mdx +++ b/src/content/docs/aegis/analytics.mdx @@ -7,10 +7,9 @@ sidebar: import { Type } from "~/components"; -Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data on your Aegis IPs utilization, and monitor their capacity. As explained in [IPs allocation](/aegis/about/ips-allocation/), each Aegis IP can support 40,000 concurrent connections per origin IP. - -Refer to the GraphQL Analytics API documentation for guidance on how to [get started](/analytics/graphql-api/getting-started/). The specific Aegis schema is called `aegisIpUtilizationAdaptiveGroups`. +Use the [GraphQL API](/analytics/graphql-api/) to get aggregate data and monitor your Aegis IPs capacity. As explained in [IPs allocation](/aegis/about/ips-allocation/), each Aegis IP can support 40,000 concurrent connections per origin IP. +Refer to the GraphQL Analytics API documentation to [get started](/analytics/graphql-api/getting-started/). The specific Aegis schema is called `aegisIpUtilizationAdaptiveGroups`. You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions: From c6c5d0efe67e2345989a332ab909fb43bc1a4434 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Fri, 9 May 2025 16:22:21 +0100 Subject: [PATCH 3/3] Add missing periods --- src/content/docs/aegis/analytics.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/aegis/analytics.mdx b/src/content/docs/aegis/analytics.mdx index 40045bdd0dd9ce..d78bcf98a64f03 100644 --- a/src/content/docs/aegis/analytics.mdx +++ b/src/content/docs/aegis/analytics.mdx @@ -20,10 +20,10 @@ You can get average (`avg`) or maximum (`max`) utilization values (in percentage - The Cloudflare point of presence (PoP). For example, `sjc`. - `egressIp` - - Your assigned Aegis IP. For example, `192.0.2.1` + - Your assigned Aegis IP. For example, `192.0.2.1`. - `origin` - Origin IP and port. For example, `203.0.113.150:443`. - `popUtilizationKey` - - The Cloudflare point of presence (PoP), the Aegis IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443` + - The Cloudflare point of presence (PoP), the Aegis IP, and the origin IP and port. For example, `sjc 192.0.2.1 203.0.113.150:443`.