{
  "id": 13560054,
  "title": "Defensive Rollback Gates for Malformed Metrics Query JSON Responses",
  "url": "https://urgent.news/2026/10/10/defensive-rollback-gates-for-malformed-metrics-query-json-responses",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-10T22:20:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/yannicksterling6563/defensive-rollback-gates-for-malformed-metrics-query-json-responses-11a9"
  },
  "original_language": "en",
  "account": "The source material discusses defensive parsing techniques for malformed metrics query JSON responses in a rollout experiment with tenant cohorts. Key points include treating malformed or partial responses as unknown, retaining the last successful poll timestamp, logging rejected payloads for diagnosis, and using error-group polling as a fallback when metrics parsing repeatedly fails. The article emphasizes not overestimating green results from incomprehensible data, as it can give false assurance and allow wider exposure. It outlines a process for validating JSON responses, distinguishing malformed polls from sustained loss of evidence, and defining SLOs around rollout state and failure escalation. The source also provides a Go code example demonstrating how to separate request uncertainty from response uncertainty and validate parsed responses before making decisions about further rollout expansion.",
  "summary": "Rollback safety changes the design: an alert worker must treat a malformed or partial metrics query response as unknown, never healthy . For a gaming experiment split across tenant cohorts, validate every response before comparing thresholds, retain the last successful poll timestamp, log enough of a rejected payload to diagnose the contract mismatch, and use error-group polling as the…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}