{
  "id": 7144795,
  "title": "Observability in the frontend: HTTP 200 hides ~900 empty catches",
  "url": "https://urgent.news/2026/09/13/observabilidade-no-frontend-o-http-200-esconde-900-catch-vazios",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-13T17:51:10.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tiagovilasboas/observabilidade-no-frontend-o-http-200-esconde-900-catch-vazios-53jd"
  },
  "original_language": "pt",
  "account": "A software developer encountered issues with error detection and monitoring while implementing a payment checkout system. Despite receiving an HTTP 200 response, users experienced errors, which were not caught by the monitoring system due to empty catch blocks. The developer implemented a solution using Sentry, setting specific sampling rates and tags to track errors, and achieved better error detection and monitoring. The solution involved setting up a contract for error tracking, including domain and flow tags, and ensuring that error detection was not limited to just backend metrics.",
  "summary": "Abri o checkout e o BFF de pagamento devolveu HTTP 200. No botão, TypeError. Seller e comprador falhavam sem stack, sem release, sem rota. Infra já tinha métrica. O navegador, onde o dinheiro vive, era ponto cego. Eu contei da ordem de ~900 catch vazios ou logs que engoliam a exceção. Quatro fronts. Sem dono. Se eu ligasse o SDK no default do wizard, ia queimar quota e ainda assim não ter golden…",
  "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."
}