What happens to one line of your log

From the game writing it to the guild seeing it

What happens to one line of your log From the game writing it to the guild seeing it 01 / The game writes 02 / Privacy filter 03 / Your machine 04 / Transit and ingest 05 / Where it lands EQ log file · a line at a time · 01 / The game writes · authoritative EQ log file a line at a time authoritative Zeal pipe · gauges, fast · 01 / The game writes · no identity Zeal pipe gauges, fast no identity Byte filter · before parsing · 02 / Privacy filter · opt-out aware Byte filter before parsing opt-out aware Never uploaded · officer, tells, group · 02 / Privacy filter · discarded Never uploaded officer, tells, group discarded Trackers · charm, threat, buff · 03 / Your machine · in memory Trackers charm, threat, buff in memory Your overlays · 15 windows · 03 / Your machine · local only Your overlays 15 windows local only Durable queue · survives restart · 04 / Transit and ingest · retry, backoff Durable queue survives restart retry, backoff Bot ingest · budgeted · 04 / Transit and ingest · bearer auth Bot ingest budgeted bearer auth Merged parse · one card per fight · 05 / Where it lands · max per player Merged parse one card per fight max per player Discord · boards, alerts · 05 / Where it lands · projection Discord boards, alerts projection raw lines unread private channels dropped kept parsed health, target live no round trip instant shareable only consented retries at-least-once merge deduped post deferred Legend primary data policy / PII data store data flow

Dropped, not withheld

  • • The filter matches bytes before the parser runs
  • • Officer chat, tells and group are never in memory to leak

One fight, every viewpoint

  • • Each raider uploads only what their own client saw
  • • The merge keeps the maximum per player, so nobody double-counts

The queue is the reason nothing is lost

  • • Every upload persists to disk before it is sent
  • • A dead network delays a parse; it does not lose one