{
  "acceptance": "A report can be traced to its saved configuration and observed fields. The investigation distinguishes browser-reported failures, infrastructure findings and information that remains unavailable.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "NEL is marked experimental and requires checking browser compatibility."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "NEL permits reports about network fetches from supporting browsers."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "NEL reports use a reporting group defined through Report-To."
    }
  ],
  "description": "Treat Network Error Logging as an additional browser signal and preserve its support and reporting limits.",
  "diagram": [
    "Supporting browser and policy",
    "Reported network observation",
    "Correlate infrastructure evidence",
    "State coverage and missing signals"
  ],
  "draft_hash": "1bd97bd9aa4871437c776a6639e0a60253646519a8ba7ea6231d1119f7914f1b",
  "evidence": {
    "observed_at": "2026-11-02T21:30:34.153973+00:00",
    "period": {
      "end": "2026-11-02T21:30:34.153973+00:00",
      "start": "2026-11-02T21:30:34.153973+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Confirm support and the deployed reporting policy.",
    "Preserve the failure phase and reported timestamp.",
    "A missing HTTP response may require another evidence source.",
    "Silence does not prove that all clients succeeded."
  ],
  "figure_title": "Use network-error reports without assuming complete coverage",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "network-error-logging-evidence-limits",
  "interpretation": "MDN labels Network Error Logging experimental and describes reports from supporting browsers about failed, and optionally successful, network fetches. That scope matters: a received report is evidence of a reported observation within the mechanism, while silence does not prove that every client succeeded. Before adding the data to an Analytics report, document browser support, the policy configuration and the reporting endpoint that supplied the records.",
  "keyword_volume": "Not obtained",
  "limits": "Experimental support and reporting behavior can change. Do not infer universal browser coverage, customer impact or AI crawler behavior from this signal. No failure test is claimed to have been run here.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/network-error-logging-evidence-limits/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A browser network-error report is being treated as a complete census of failed visits or crawler failures.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T06:10:12.056883+00:00",
  "reader": "Site owners and analysts investigating a browser network-error report is being treated as a complete census of failed visits or crawler failures.",
  "related": [
    "collector-heartbeat-vs-zero-traffic"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/collector-heartbeat-vs-zero-traffic/",
      "title": "Distinguish zero traffic from a collection failure"
    }
  ],
  "research_document_ids": [
    "ecf471ef24f449ed10121a44dd68f432"
  ],
  "slug": "network-error-logging-evidence-limits",
  "source_signature": "964b76db1a622d2e76c4b45523fdd104820ddc1b42767366c887fd0285bf5a83",
  "sources": [
    {
      "hash": "d641b9b203698fa931e8c13491ccb35a484fc4567722aaeb6f08a9361b5e36fd",
      "locator": "Network Error Logging (NEL) / b1; Network Error Logging (NEL) / b2; Network Error Logging (NEL) / b3",
      "observed_at": "2026-11-02T21:30:34.153973+00:00",
      "title": "Network Error Logging (NEL)",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Network_Error_Logging"
    }
  ],
  "sources_required": [],
  "steps": [
    "Confirm the current browser support and your actual NEL configuration before relying on this mechanism. Treat it as an optional signal rather than the only availability monitor.",
    "Inspect a small authorized report sample and document the fields actually available. Review URLs, referrers and network details for sensitive data before storing or sharing the sample.",
    "Correlate the reported time and failure phase with authorized infrastructure records. Keep absent application requests as absent evidence instead of assigning invented HTTP statuses.",
    "Run a controlled, non-production failure test if your environment permits it. Verify report receipt and retention, then describe exactly which client and failure were tested."
  ],
  "title": "Use network-error reports without assuming complete coverage",
  "worked_example": "Hypothetical example: a controlled browser reports a DNS-related failure while the application access log has no corresponding HTTP response. That is a useful lead for a network investigation. It is not evidence that the application returned a particular error status, and it does not establish how many unobserved clients encountered the same problem. The example illustrates cross-source reasoning, not a measured outage."
}