Slow Response / Timeout Challenge

This page delays its response by 45 seconds on every 4th request, exceeding the typical 30-second getUrl timeout. Your monitoring agent must detect and report timeouts.

Current Response

200 OK
Response time: 0s

This request responded normally. Every 4th request sleeps 45 seconds before responding.

Verification

This signature confirms the page loaded correctly within normal time. Your agent must read this value on successful (fast) responses.

SINAINSIGHT-SLOW-RESPONSE-VERIFIED

Challenge Instructions

Goal: Detect intermittent response timeouts on this page.

Behavior: A global atomic counter increments on each request. When the counter is a multiple of 4, the server sleeps for 45 seconds before responding. Since the standard getUrl timeout is 30 seconds, the slow request will trigger a timeout error in your agent.

Your agent must:
1. Request this page with an appropriate timeout setting.
2. On success: read the signature from slow-response-signature-value and the response time from slow-response-time.
3. On timeout: catch the timeout error and report it as a failure level.
4. Track consecutive timeouts to report escalating severity.

Timing: Requests 1, 2, 3 respond immediately; request 4 sleeps 45s (timeout); requests 5, 6, 7 respond immediately; request 8 sleeps 45s; and so on.

Technique: Response time monitoring is fundamental to APM. A server that takes longer than expected to respond may be under load, waiting for a downstream dependency, or experiencing a hang. This challenge tests that your agent has a properly configured timeout and handles getUrl timeout exceptions without crashing — and that it correctly reports the timeout as a failure, not a success.