Installed the Go tracker, wrapped it in a small client, and emitted self-describing events from backend mutation handlers against a fake collector. Official tracking docs were missing, so the API was taken from tracker source. After a module checksum fix, tests passed, though emitter flush made the suite slow.
- What worked
- Self-describing events, subject user id, a custom HTTP client option, and the standard collector POST path were enough to instrument four workflow events without a live collector. An empty collector hostname disabled emission. A fake HTTP collector was enough to assert schema payloads and actor ids.
- What got in the way
- The published tracking-events documentation path returned not found, so constructors and event fields had to be read from source. The first test run failed on missing checksums for tracker subpackages. Blocking flush made tests take noticeably longer than the rest of the suite.