{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-SENTRY-OUTCOMES-01-v1",
  "record_kind": "external_reference",
  "title": "Sentry outcomes: Missing events need ingestion context",
  "system": "Sentry",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an empty Sentry event search prove that no error occurred?",
  "near_questions": [
    "Can Sentry receive an event and still drop it?",
    "Which outcome indicates filtering?",
    "Which outcome indicates rate limiting?",
    "Are accepted counts filtered in the same way?",
    "What interval and dataset were queried?",
    "Does the experimental API have a stable contract?",
    "Can client-side losses be absent from server counts?",
    "Were project or environment filters applied?",
    "Does accepted volume equal complete application coverage?",
    "What explains a missing stored event?",
    "When should an agent refuse a no-error conclusion?",
    "Can I save the event-coverage review?"
  ],
  "supported_claims": [
    {
      "claim": "The reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "The reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Sentry accepted and dropped event outcomes",
    "source_url": "https://docs.sentry.io/api/explore/query-dropped-and-accepted-events-stats-by-outcome-and-reason/",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SENTRY-OUTCOMES-01-v1",
    "candidate_record_sha256": "d38677f21e5faac932eb9bc05299efceb60cfbcf13f738c773cb9e0a4838c8b5",
    "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 reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.",
    "required_buyer_context": "Experimental API version, collection scope, outcomes and query interval. Effective buyer configuration and dated operational evidence are required.",
    "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-16",
    "claim_to_check": "No matching stored events proves no application error occurred.",
    "documented_statement": {
      "status": "documented",
      "statement": "The reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.",
      "source_ids": [
        "sentry-outcomes"
      ]
    },
    "buyer_evidence_required": [
      "SDK/ingestion coverage.",
      "Accepted and dropped outcomes for the interval.",
      "Filters, quotas and query scope."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require collection and outcome evidence before making an absence claim."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "sentry-outcomes",
        "url": "https://docs.sentry.io/api/explore/query-dropped-and-accepted-events-stats-by-outcome-and-reason/",
        "final_url": "https://docs.sentry.io/api/explore/query-dropped-and-accepted-events-stats-by-outcome-and-reason/",
        "title": "Sentry accepted and dropped event outcomes",
        "checked_on": "2026-10-16",
        "sha256": "d352dd497d4caa05e8e5603ffe0545dbd0cb0b9e56cf88f6472a7d0a570db792",
        "bytes": 232193
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Preserve the ingestion limitations behind a monitoring or incident-evidence conclusion.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Experimental API version, collection scope, outcomes and query interval"
    }
  },
  "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#sentry-dropped-event-coverage-boundary",
  "machine_readable_record": "/varexis-index/records/sentry-dropped-event-coverage-boundary.json"
}