httpjson Degraded status: separate an optional rate-limit header from failed polling
An absent optional header is different from failed polling.
What the warning should mean
An absent optional header is different from failed polling. Compare health labels with the service’s header contract and the actual request outcome. Truthound can check that prepared correspondence, but suppressing real 429 or network failures to remove noise would create a different operational error. [1, 2, 3]
The reporter-path difference
Beats #53565 is a Bug Hunter test report where a missing optional limit header produces Degraded in the percentage early_limit branch. It concerns misleading health status rather than observed data loss. The reported distinction is between the ignore-empty reporter and the reporter used by that branch; the automated test does not establish operating-data completeness. [1]
Do not invent a value for an absent header
Show header requirements, request success and approved health label together. Isolate Degraded states caused solely by the optional header’s absence. Record whether percentage early_limit applies, retain other errors and avoid filling a missing header as limit=0, which would change its optional meaning. [1, 3]
A conditional expectation of Healthy
The illustrative contract makes the limit header optional; the request succeeds with no other error. Expected label is Healthy. Healthy meets this condition; Degraded fails it. Do not substitute limit=0 for absence or impose Healthy where the header is mandatory or a real failure occurred. [1, 3]
Who defines status meaning
Truthound Core Python SDK 3.3.2 can compare prepared policy_health_label and reported_health_label with ColumnPairValidator using relationship="==". The API owner defines requirements and success semantics, and the operator supplies non-missing labels. The SDK does not change the limiter or Agent state, and matching Healthy labels do not prove complete capture. [1, 2, 3]
Different evidence for health and data
Observe request success, 429 responses and waiting behavior independently, and test the reporter change in a bounded environment. Missing required headers or network failures can legitimately justify Degraded. Explain status accuracy and data quality with their respective evidence. [1, 3]
Application conditions
Confirm the API’s optional-header contract and successful response, distinguishing percentage early_limit handling.
Alternatives
Observe request outcomes and waiting separately, then test the reporter correction on a bounded setup.
Limitations
The SDK does not change rate limiting or Agent health; matching Healthy labels do not prove completeness or quota compliance.
Evidence
- Event checked
- Subject checked
- Modified
