Skip to content

[Aegis] Document available GraphQL analytics #22300

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
May 13, 2025
+31 −0
Merged

[Aegis] Document available GraphQL analytics #22300

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ec4f60d
Create new anaytics page and fill in content
RebeccaTamachiro May 8, 2025
6809915
Cross-link with ips-allocation and info on concurrent connections
RebeccaTamachiro May 8, 2025
c6c5d0e
Add missing periods
RebeccaTamachiro May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/aegis/about/ips-allocation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
29 changes: 29 additions & 0 deletions src/content/docs/aegis/analytics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
title: Analytics
pcx_content_type: reference
sidebar:
order: 7
---

import { Type } from "~/components";

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:

- `datetimeFiveMinutes` <Type text="time" />
- Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.

- `popName` <Type text="string" />
- The Cloudflare point of presence (PoP). For example, `sjc`.

- `egressIp` <Type text="string" />
- Your assigned Aegis IP. For example, `192.0.2.1`.

- `origin` <Type text="string" />
- Origin IP and port. For example, `203.0.113.150:443`.

- `popUtilizationKey` <Type text="string" />
- 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`.
Loading