Server Error Handling Challenge

This page returns HTTP 500 on every 4th request. Your monitoring agent must handle transient server errors gracefully and detect when a page is intermittently failing.

Current Response

200 OK

This is a normal response. Every 4th request to this page returns HTTP 500.

Verification

This signature confirms the page loaded correctly with HTTP 200. Your agent must read this value on successful responses.

SINAINSIGHT-SERVER-ERROR-VERIFIED

Challenge Instructions

Goal: Detect intermittent HTTP 500 errors on this page.

Behavior: A global atomic counter increments on each request. When the counter is a multiple of 4, the server returns HTTP 500 with an error page instead of the normal 200 response.

Your agent must:
1. Request this page and check the HTTP status code.
2. On HTTP 200: read the signature from server-error-signature-value.
3. On HTTP 500: read the error from server-error-status and server-error-message.
4. Report the correct level based on whether the last N requests succeeded or failed.

Expected behavior: Requests 1, 2, 3 succeed (HTTP 200); request 4 fails (HTTP 500); requests 5, 6, 7 succeed; request 8 fails; and so on.

Technique: Real-world APM agents must handle non-200 HTTP responses without crashing or silently succeeding. A probe that only checks for a page element without verifying the status code will miss intermittent 5xx errors. This challenge tests that your agent correctly inspects the HTTP status and reports failure when the server signals an error.