{
 "schema_version": 1,
 "generated": "2026-10-23",
 "id": "ghuntley-preflight--trace-one-request-across-both-proxies",
 "repo": "ghuntley/preflight",
 "repo_url": "https://github.com/ghuntley/preflight",
 "repo_slug": "ghuntley-preflight",
 "title": "Trace one request across Preflight and underclass",
 "page_title": "How to trace one request across Preflight and underclass with Preflight",
 "summary": "Use the shared x-request-id to follow a single request through both proxy logs.",
 "who": "An engineer debugging a failed agent call who needs to see whether Preflight blocked it or underclass failed upstream.",
 "problem": "Two proxies in sequence make it hard to tell which one handled a failing request.",
 "outcome": "Searching one request_id in both services shows the full path from ingress to upstream response.",
 "steps": [
  "Send a request through `http://127.0.0.1:8081/v1` and note the `x-request-id` in the response headers",
  "Search the Preflight JSON logs for that value in the `request_id` field",
  "Search the underclass logs for the same value",
  "Compare `request.policy_completed` status with the underclass response status",
  "Check `curl http://127.0.0.1:8081/metrics` for aggregate counters if you need totals (inferred, check the README)"
 ],
 "agent_prompt": "Using the preflight repo at github.com/ghuntley/preflight, send one request to http://127.0.0.1:8081/v1/responses, capture the x-request-id header, and search both preflight and underclass logs for that ID. Report the status recorded by each service and verify that the IDs match.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "The request ID is diagnostic metadata only and is not proof that inspection ran, so check the finding events for that.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "rust",
 "requirements": [
  "A running underclass instance on 127.0.0.1:8080",
  "Nix (for `nix run`) or devenv and Cargo for a local checkout",
  "A coding harness or client that can change its base URL to http://127.0.0.1:8081/v1",
  "Bubblewrap available for the default sandboxed attachment workers"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.6,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/ghuntley-preflight/trace-one-request-across-both-proxies/",
 "md": "https://dedupedai.com/use-cases/ghuntley-preflight/trace-one-request-across-both-proxies/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/ghuntley-preflight--trace-one-request-across-both-proxies.json",
 "api_version": "v1"
}