Send structured log lines from your app to the Logs page. Logs show only what your app sends, plus a warning whenever TraceIQ rejects one of your SDK deliveries (for example an invalid write key), so you know data isn't arriving.

Browser / games: entries are buffered, sent in batches, and tagged with the current session (so they link to its replay) and user:

traceiq.log('info', 'Level 3 started', { level: 3 });
traceiq.log('error', 'Level 3 assets failed to load', {
  service: 'game-client',   // optional, defaults to "web-client"
  error,                    // optional Error: its stack is attached
  level: 3,                 // anything else becomes searchable metadata
});

Node: inside traceiq.middleware() each log carries the current request's request and trace IDs, so it appears on that request in the Requests explorer:

const traceiq = new TraceIQ({ projectId: 'YOUR_PROJECT_ID', writeKey, serviceName: 'game-server' });

traceiq.log('warn', 'Matchmaking queue is backing up', { queued: 412 });
await traceiq.shutdown(); // flushes events and logs

Any other runtime can post directly to POST https://api.traceiq.run/v1/logs/batch with the x-traceiq-write-key header and a body of { projectId, logs: [{ level, message, … }] } (up to 100 entries).

To read logs from the terminal, use the CLI:

traceiq logs --level error --since 24h
traceiq logs --search checkout --follow