Skip to content

Commit 7639314

Browse files
committed
Adds example
1 parent 146a584 commit 7639314

File tree

1 file changed

+89
-0
lines changed

1 file changed

+89
-0
lines changed

src/content/docs/load-balancing/reference/load-balancing-analytics.mdx

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,95 @@ To view latency information for your load balancer, go to **Traffic** > **Load B
5757
When a Monitor Group is attached to a pool, each logged health event includes the `monitors` field.
5858
This field lists the individual monitors within the group and their results, making it easier to see which monitor contributed to a status change.
5959

60+
Example event (truncated):
61+
62+
```json
63+
{
64+
"id": <id>,
65+
"timestamp": "2025-09-22 19:22:00",
66+
"pool": {
67+
"id": "<id>",
68+
"name": "example-monitor-group-test-pool-us",
69+
"healthy": true,
70+
"changed": false,
71+
"minimum_origins": 1
72+
},
73+
"origins": [
74+
{
75+
"name": "origin-a",
76+
"ip": "192.0.2.10",
77+
"enabled": true,
78+
"healthy": true,
79+
"failure_reason": "No failures",
80+
"response_code": 200,
81+
"monitors": [
82+
{
83+
"id": "<id>",
84+
"healthy": true,
85+
"failure_reason": "No failures",
86+
"response_code": 200,
87+
"must_be_healthy": true,
88+
"monitoring_only": false
89+
},
90+
{
91+
"id": "<id>",
92+
"healthy": true,
93+
"failure_reason": "No failures",
94+
"response_code": 200,
95+
"must_be_healthy": true,
96+
"monitoring_only": false
97+
},
98+
{
99+
"id": "<id>",
100+
"healthy": false,
101+
"failure_reason": "HTTP timeout occurred",
102+
"must_be_healthy": false,
103+
"monitoring_only": true
104+
}
105+
]
106+
},
107+
{
108+
"name": "origin-b",
109+
"ip": "198.51.100.25",
110+
"enabled": true,
111+
"healthy": false,
112+
"failure_reason": "TCP connection failed",
113+
"changed": true,
114+
"monitors": [
115+
{
116+
"id": "<id>",
117+
"healthy": false,
118+
"failure_reason": "TCP connection failed",
119+
"must_be_healthy": true,
120+
"monitoring_only": false
121+
},
122+
{
123+
"id": "<id>",
124+
"healthy": true,
125+
"failure_reason": "No failures",
126+
"response_code": 200,
127+
"must_be_healthy": true,
128+
"monitoring_only": false
129+
},
130+
{
131+
"id": "<id>",
132+
"healthy": false,
133+
"failure_reason": "HTTP timeout occurred",
134+
"must_be_healthy": false,
135+
"monitoring_only": true
136+
}
137+
]
138+
}
139+
]
140+
}
141+
```
142+
143+
In this example:
144+
145+
- Each origin includes a `monitors` array listing all monitors within the attached group.
146+
- Fields such as `must_be_healthy` `and monitoring_only` indicate each monitor's role in determining the origin's overall health.
147+
- The `healthy` and `failure_reason` fields show which individual monitor checks succeeded or failed.
148+
60149
To access logs in the dashboard, go to **Traffic** > **Load Balancing Analytics**.
61150

62151
## GraphQL Analytics

0 commit comments

Comments
 (0)