{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T21:43:00.943093Z",
  "record_id": "VXI-EXT-ICE06-AZURE-LOGEXPORT-FAILURE-METRIC-INTERPRETATION-01-v1",
  "record_kind": "external_reference",
  "title": "Azure logexport failure metric interpretation",
  "system": "Microsoft",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does the Azure Export Failures metric count permanently missing log records?",
  "near_questions": [
    "Azure Export Failures metric not lost records",
    "failed export attempts versus missing events",
    "Log Analytics retry metric interpretation",
    "audit collection error count uncertainty"
  ],
  "supported_claims": [
    {
      "claim": "The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Do not relabel failed-attempt counts as lost records or infer zero loss from an unexamined metric.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Microsoft: Log Analytics workspace data export",
    "source_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-data-export",
    "checked_on": "2026-10-29",
    "candidate_record_id": "VXI-EXT-ICE06-AZURE-LOGEXPORT-FAILURE-METRIC-INTERPRETATION-01-v1",
    "candidate_record_sha256": "df14902015a7d91f165df32f1ed51a2ee0e80f6e9a546b4b354a0eca444e91d0",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.",
    "required_buyer_context": "metric definition and time window; retry outcomes; destination delivery evidence; source reconciliation. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-29",
    "claim_to_check": "Does the Azure Export Failures metric count permanently missing log records?",
    "documented_statement": {
      "status": "documented",
      "statement": "The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.",
      "source_ids": [
        "azure-logexport"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A reporting system turns export errors into a count of missing audit events. The incident report can overstate or understate actual evidence loss. Adds aggregate-attempt interpretation, separate from query-level partial errors or documented possible pipeline loss. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "azure-logexport"
      ]
    },
    "buyer_evidence_required": [
      "metric definition and time window",
      "retry outcomes",
      "destination delivery evidence",
      "source reconciliation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not relabel failed-attempt counts as lost records or infer zero loss from an unexamined metric."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "azure-logexport",
        "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-data-export",
        "final_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-data-export",
        "captured_at_utc": "2026-10-29T19:10:38.279289+00:00",
        "status": 200,
        "content_type": "text/html",
        "bytes": 126846,
        "sha256": "63a6c760f85f957c13808826a22cae4da4dc7f78a8b2bf0c96a6734e7cbeec37",
        "publisher": "Microsoft",
        "version_context": "Rolling official documentation; applicability is limited to the exact captured response and its stated service, API and feature constraints. Recheck present support before current reliance. Source captured 2026-10-29T19:10:38.279289+00:00.",
        "rights_review": "Public original factual paraphrase and attributed source metadata only. Captured documentation bodies, code examples, images and vendor marks remain private. No vendor software licence, certification or buyer deployment assurance is granted.",
        "capture_integrity_verified": true,
        "source_assertion_reviewed": true,
        "title": "Microsoft: Log Analytics workspace data export",
        "checked_on": "2026-10-29",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response body bytes",
        "reviewed_sections": [
          "starting from the configuration time",
          "Data completeness",
          "Unsupported tables",
          "Export Failures"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "A reporting system turns export errors into a count of missing audit events. The incident report can overstate or understate actual evidence loss.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "Export Failures"
    },
    "buyer_relevance": "A reporting system turns export errors into a count of missing audit events. The incident report can overstate or understate actual evidence loss.",
    "refusal_conditions": [
      "Do not relabel failed-attempt counts as lost records or infer zero loss from an unexamined metric.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "Audit and evidence-accountability operator",
      "scenario": "A reporting system turns export errors into a count of missing audit events.",
      "consequence": "The incident report can overstate or understate actual evidence loss.",
      "confidence": "Primary documentation assertion supported; deployment applicability unverified"
    },
    "novelty_review": {
      "candidate_id": "ICE06-012DF82A5809",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-AZURE-LOGS-HTTP-200-PARTIALERROR-EVIDENCE-01-v1",
      "nearest_record_url": "/varexis-index/records/azure-logs-http-200-partialerror-evidence.json",
      "nearest_record_sha256": "7bb289da0605cd7b5403e7b73b41e85f85e85d5dd35a71321b78fe0ba512a8f7",
      "material_distinction": "Adds aggregate-attempt interpretation, separate from query-level partial errors or documented possible pipeline loss.",
      "independent_challenge": "PASS"
    },
    "optional_selection": {
      "guide_id": "agent-tool-change-execution-provenance",
      "guide_url": "/index-guides/agent-tool-change-execution-provenance",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": {
        "product_id": "agent-audit-coverage",
        "price_gbp_excluding_vat": 79,
        "purchase_url": "/index-access?route=agentic_pack_audit_coverage_v1",
        "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
        "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
      },
      "boundary": "Optional adjacent workflow only. This review does not extend a checker input schema or implement native provider validation. Preserve the six canonical guides unchanged."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE06-AZURE-LOGEXPORT-FAILURE-METRIC-INTERPRETATION-01-v1"
      },
      "record_url": "/varexis-index/records/azure-logexport-failure-metric-interpretation.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice06-audit",
    "label": "Audit, Provenance & Evidence Accountability",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "A reporting system turns export errors into a count of missing audit events. The incident report can overstate or understate actual evidence loss.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#azure-logexport-failure-metric-interpretation",
  "machine_readable_record": "/varexis-index/records/azure-logexport-failure-metric-interpretation.json"
}