We Recovered Unreal Insights OTLP Export Through a Corporate HTTPS Proxy During Q4 Diligence Week - 2026 Case Study

Monday on home Wi-Fi: Unreal Insights captures a clean frame timeline; OTLP spans land in the collector. Tuesday on corporate VPN: the same packaged build opens fine, but OTLP export times out and diligence dashboards stay empty. Wednesday partner call: "Where is your trace receipt?"

This is a synthesized case study—a field pattern across Q4 2026 micro-studios shipping Unreal Engine 5.6 fest demos who enabled Insights / Trace for diligence but hit MITM HTTPS proxies on laptops used during partner week. It is not a named studio turnaround. There are no invented funding outcomes, no fake Slack quotes, and no made-up span counts.

What follows is the failure signature, the proxy policy decision (pin CA vs offline batch), gates O1–O6, artifact unreal_otlp_diligence_receipt_v1.json, and how the pattern maps to your project if traces work locally but egress dies behind VPN.

Pair with Q4 telemetry diligence analysis, Unity UGS OTLP preflight (cousin engine lane), Lesson 260 UGS OTLP BUILD_RECEIPT, planned Guide #36 Unreal OTLP preflight, and Lesson 274 forward BUILD_RECEIPT milestone.

Non-repetition note: Lesson 260 owns Unity UGS privacy URL + ugs_otlp_diligence_receipt_v1. Q4 diligence blog owns 07-observability/ annex strategy. This URL owns Unreal Insights OTLP egress behind corporate proxy—recovery narrative, not another ninety-second preflight checklist.

Why this matters now (Q4 diligence week / December 2026)

1. Partners ask for traces — After Q3 evidence packets, Q4 diligence expects 07-observability/ rows—not "we use Insights" in a slide.
2. Local trace ≠ export proof — Insights UI on a dev machine does not archive in partner zips.
3. Corporate VPN week — Founders demo from accelerator space or publisher offices; MITM proxies break default TLS trust.
4. Unity cousins already filed — Teams with Unity SKUs ship UGS OTLP receipts; Unreal SKUs need parallel unreal_otlp_diligence_receipt_v1.
5. Fest hotfix cadence — BUILD_RECEIPT build_label bumps without re-exporting traces reads as observability theater.

Direct answer: Recovery required documenting proxy policy (CA pin or offline batch), exporting at least one redacted trace sample to 07-observability/offline_traces/, filing unreal_otlp_diligence_receipt_v1.json with gates O1–O6, and wiring unreal_otlp_diligence_ok on BUILD_RECEIPT before the partner zip ships.

Who this case study is for

Engines: Unreal 5.4+ with Insights / Trace and OTLP-compatible collector (internal or vendor).
Time: ~90 minutes first recovery sprint; ~15 minutes when proxy policy template exists.

Beginner quick start — offline batch vs pin CA

You do not need to become a network engineer. Pick one path:

Success check: A producer can open 07-observability/README.md, find offline_traces/sample_YYYYMMDD.json or otlp_live_probe.log, and see unreal_otlp_diligence_ok: true without asking engineering to "open Insights."

Fail-closed: Do not claim live dashboards in partner email if only offline batch passed O5—README must say mode: offline_batch.

The diligence-facing failure (typical signals)

Internal language before fix: "Tracing is enabled in DefaultEngine.ini" — configuration without egress proof.

Starting state (what was wrong)

Gameplay and crash symbolication were fine. Trace export credibility was not.

Root cause pattern (synthesized)

Three recurring mechanics—often combined:

None require malice—only missing proxy policy in 07-observability/README.md.

Timeline (five working days — pattern timing)

Teams with existing Unity UGS preflight template recovered in two days; greenfield Unreal-only teams took five.

Hour-by-hour D1 (reproduction discipline)

If home GREEN and VPN RED—you are in this case study.

D2 — Corporate proxy policy table

File 07-observability/proxy_policy_table.md (or embed rows in README):

Pass: Every row has an owner initials column in internal copy; public zip redacts employee names.

Beginner decision tree (pin vs batch)

IT gave corp-root.pem within 24h?
  yes → Pin CA (D3 path A); live OTLP probe must pass on VPN
  no  → Offline batch (D3 path B); README states live export deferred
Partner demands live only?
  escalate IT ticket with otlp_probe_fail.log attachment
  do not fake live_ok in receipt

D3 path A — CA pin (working dev)

Linux / macOS launcher

export OTEL_EXPORTER_OTLP_ENDPOINT="https://otel-collector.internal:4318"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export SSL_CERT_FILE="/etc/ssl/corp-root.pem"
export SSL_CERT_DIR="/etc/ssl/certs"

Windows PowerShell (fest demo launcher)

$env:OTEL_EXPORTER_OTLP_ENDPOINT = "https://otel-collector.internal:4318"
$env:SSL_CERT_FILE = "C:\certs\corp-root.pem"
# Optional: import corp root to Local Machine\Trusted Root Certification Authorities

Probe before Insights export

curl -v --cacert /etc/ssl/corp-root.pem \
  -X POST "https://otel-collector.internal:4318/v1/traces" \
  -H "Content-Type: application/x-protobuf" \
  --data-binary @empty_trace.pb 2>&1 | tee otlp_probe_pass.log

Pass: HTTP 200 or collector-specific 202—not TLS handshake failure.

Unreal Insights export hook

Document in receipt which path you used:

Pin engine version in build_label README—UE 5.4 vs 5.6 exporter defaults differ.

D3 path B — offline trace batch (beginner-friendly)

When IT cannot ship CA before partner zip:

1. Capture .utrace on home machine (known-good path).
2. Convert or export OTLP JSON slice per OpenTelemetry trace JSON docs—redact user paths and machine names.
3. Store under 07-observability/offline_traces/batch_YYYYMMDD.json.
4. README row: "Live OTLP blocked on corporate VPN 2026-11-18–2026-11-22; offline batch represents fest-demo-2026-11-rc4 golden path."

Pass: File exists; build_label in batch metadata matches player-visible label; no PII.

Honest limit: Offline batch proves you can produce trace artifacts—partners may still ask for live policy before term sheet. Do not mislabel mode in receipt.

Developer path — gates O1–O6

unreal_otlp_diligence_receipt_v1.json

Pin at release-evidence/telemetry/UNREAL_OTLP_DILIGENCE_RECEIPT.json and copy into 07-observability/:

{
  "schema": "unreal_otlp_diligence_receipt_v1",
  "build_label": "fest-demo-2026-11-rc4",
  "engine_version": "5.6.0",
  "insights_session_id": "trace-session-20261118-golden",
  "otlp_endpoint": "https://otel-collector.internal:4318/v1/traces",
  "otlp_mode": "offline_batch",
  "corporate_proxy": {
    "required": true,
    "mitm_https": true,
    "ssl_cert_file": null,
    "offline_batch_path": "07-observability/offline_traces/batch_20261118.json",
    "probe_fail_log": "07-observability/otlp_probe_fail.log"
  },
  "privacy_crosswalk": {
    "store_about_privacy_url": "https://yourstudio.com/privacy",
    "notes": "Unreal SKU—no UGS; privacy URL still required for store parity"
  },
  "cousin_receipts": {
    "diligence_telemetry": "07-observability/diligence_telemetry_receipt_v1.json",
    "crash_symbolicate": "07-observability/crash_symbolicate_receipt_v1.json",
    "unity_ugs_otlp": "release-evidence/telemetry/UGS_OTLP_DILIGENCE_RECEIPT.json"
  },
  "gates": {
    "O1_insights_configured": "pass",
    "O2_otlp_documented": "pass",
    "O3_proxy_policy": "pass",
    "O4_ca_or_offline": "pass",
    "O5_sample_on_disk": "pass",
    "O6_receipt": "pass"
  },
  "unreal_otlp_diligence_ok": true,
  "telemetry_promotion_allowed": true
}

Thursday row review — optional column unreal_otlp_diligence_ok.

Unity vs Unreal cousin lane (format ladder)

Multi-SKU studios: File both receipts in 07-observability/; diligence_telemetry_receipt_v1 references cousin paths—do not merge schemas.

Proof table (synthesized recovery)

Scenarios A–G (working dev)

Diligence week operating calendar (OTLP lane)

Pair FMOD five-night challenge when audio + telemetry diligence share the same December week—orthogonal receipts, same build_label.

Privacy and redaction (non-negotiable)

Link Lesson 213 session schema for event-field hygiene—traces are a separate lane.

jq gate sketch (optional CI)

jq -e '.unreal_otlp_diligence_ok == true and .gates.O6_receipt == "pass"' \
  release-evidence/telemetry/UNREAL_OTLP_DILIGENCE_RECEIPT.json

Exit 0 before fest branch promotion when TELEMETRY_STRICT=1 in CI—cousin to GitHub Actions concurrency patterns.

Counterarguments (honest limits)

"Insights is enough for partners."
UI sessions do not archive in zips—O5 sample on disk does.

"We will fix proxy after funding."
Q4 diligence is the funding conversation for many teams—offline batch is acceptable; missing folder is not.

"Same as Unity UGS receipt."
Cousin lane—different schema, different trace surface; see table above.

"OpenTelemetry vendor handles TLS."
Vendor SDK still uses OS trust store—corp MITM breaks default chain.

Pairing with site cluster (December 2026 spine)

Two-team drill (OTLP edition)

1. Partner role: open 07-observability/ only; name otlp_mode and build_label.
2. Founder role: answer from unreal_otlp_diligence_receipt_v1.json—no screen share of Insights UI.
3. Swap: founder adds VPN probe log; partner verifies O3 proxy row exists.

Gaps in step 1 cost one evening; gaps on a live call cost term-sheet momentum.

Key takeaways

1. Local Insights trace ≠ diligence proof—export sample or probe log to disk (O5).
2. Corporate MITM breaks default TLS—pin corp CA or file offline batch honestly.
3. unreal_otlp_diligence_receipt_v1.json is distinct from Unity ugs_otlp_diligence_receipt_v1.
4. Gates O1–O6 block promotion when OTLP story is verbal only.
5. proxy_policy_table.md answers partner questions before IT tickets close.
6. otlp_mode must be live or offline_batch—never ambiguous in README.
7. Q4 diligence annex bundles child receipts via cousin_receipts paths.
8. Multi-SKU studios file Unity + Unreal cousin rows in same zip.
9. Redact PII from .utrace / JSON batches before partner send.
10. Thursday row review optional column unreal_otlp_diligence_ok.
11. Lesson 274 forward wires BUILD_RECEIPT after this narrative.
12. Fail-closed: do not email "live dashboards" when only offline batch passed.
13. VPN vs home probe matrix on D1 saves credibility on D5.
14. Engine 5.6 pin in receipt—exporter defaults drift across minors.
15. December BUILD_RECEIPT defer list when holiday freeze follows diligence week.

FAQ

Is this every Unreal team in Q4 2026?
No—synthesized from diligence-week proxy failures behind corporate VPNs; home-only teams still benefit from O6 receipt discipline.

Do we need a live OTLP collector for partners?
Not always—documented offline batch with sample file often satisfies indie asks; live-only demands require O4 CA pin success.

How is this different from Unity Lesson 260?
260 owns UGS privacy URL HEAD + ugs_otlp_diligence_receipt_v1; this case study owns Unreal Insights OTLP + unreal_otlp_diligence_receipt_v1.

What if we only use crash receipts?
File Unreal receipt with otlp_mode: not_applicable only if README honestly states no trace claims—do not claim Insights in partner deck.

Can we use the same corp CA as Unity SKU?
Yes—share ssl_cert_file path in both cousin receipts; schemas stay separate.

Does Epic provide OTLP export?
Insights / Trace tooling evolves—pin version in receipt; verify against Unreal Engine documentation for your generation.

What about Grafana Cloud?
Vendor-hosted collector still hits corp proxy—same O3–O4 policy.

Will this receipt guarantee funding?
No—it reduces perceived observability risk; outcomes vary.

Help #22 when shipped?
Will own fix OTLP proxy block steps—this case study is recovery narrative; help is procedure.

Where does PostHog fit?
PostHog evening blog is non-UGS wire-up—Unreal SKU may still file OTLP cousin if traces export.

Closing read (July 2026)

Q4 diligence taught micro-studios that crash receipts beat tool names. The follow-up ask is whether trace egress survives the same laptop your founder uses in the publisher office—not the machine on your desk at home.

Unreal teams that treat OTLP export as a receipted policy—CA pin or honest offline batch—enter partner calls with the same calm as teams who already filed Unity UGS OTLP cousins. Teams that conflate Insights UI with diligence proof learn the difference on a Wednesday call.

Start with otlp_probe_fail.log on VPN and proxy_policy_table.md—not with a collector RFP.

Email send template (OTLP annex row)

Subject: <Game> — observability v2 addendum (Unreal OTLP receipt)

Body:

We added unreal_otlp_diligence_receipt_v1.json to 07-observability/ for our UE SKU. README notes otlp_mode: offline_batch during corporate VPN week; sample trace matches fest-demo-2026-11-rc4. Unity cousin receipt included for our second SKU.

Pointer-first. Respect partner time.

Found this useful? Share the proxy policy table with your IT contact before diligence week—not after the collector times out.