Skip to content

Commit ec4f60d

Browse files
Create new anaytics page and fill in content
1 parent f3fc252 commit ec4f60d

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: Analytics
3+
pcx_content_type: reference
4+
sidebar:
5+
order: 7
6+
---
7+
8+
import { Type } from "~/components";
9+
10+
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.
11+
12+
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`.
13+
14+
15+
You can get average (`avg`) or maximum (`max`) utilization values (in percentage), and use the following dimensions:
16+
17+
- `datetimeFiveMinutes` <Type text="time" />
18+
- Timestamp truncated to five minutes. For example, `2025-01-10T00:05:00Z`.
19+
20+
- `popName` <Type text="string" />
21+
- The Cloudflare point of presence (PoP). For example, `sjc`.
22+
23+
- `egressIp` <Type text="string" />
24+
- Your assigned Aegis IP. For example, `192.0.2.1`
25+
26+
- `origin` <Type text="string" />
27+
- Origin IP and port. For example, `203.0.113.150:443`.
28+
29+
- `popUtilizationKey` <Type text="string" />
30+
- 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`

0 commit comments

Comments
 (0)