[Session] Logging

[gaearon]

This adds enough logging to key parts of the session logic that we should be able to figure out what's going on if something goes wrong. Note that agents are numbered (using WeakMap), tokens are sent as hashes (so we can trace what happens to each of them over time).

• Basic implementation
• Add gate (by stable ID)
• Send logs when the gate is on

Test Plan

Allowlist your stable ID (Statsig.getStableID()) for the debug_session gate. We'll only enable it for the few users who reported problems. Observe events rolling in. (Don't forget to turn on "Show non-production logs"!)

Note that there's a notion of separate "realms" (realmId) which correspond to browser tabs or app instances, a notion of separate "messages" (which are JSON objects describing what happened), and "slices" (which is an artifact of the transport — Statsig forces us to break apart the logs into smaller chunks or it'll refuse to send them). Since this is all for manual debugging, I think that's fine. I might write a script to reconstruct it in a readable form if needed.

Also note that this is done by stable ID so it's able to debug across account switches and logouts.

[render]

Your Render PR Server URL is https://social-app-pr-4476.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cpjs8e8l6cac73cq72dg.

[github-actions]

Old size	New size	Diff
6.3 MB	6.3 MB	1.68 KB (0.03%)

---

[estrattonbailey]

Looks great, haven't run yet though

[pfrazee]

Okay -- dont have strong opinions about how youve constructed the data you're sending up, but it does seem to function as intended. I was able to confirm the data is sending up by opting into the experiment.