Skip to main content

Read the raw event behind an issue

Log Lens stores a byte range for every occurrence instead of copying the log text. When you need the exact, unmodified bytes an occurrence was cut from - full stack trace, surrounding JSON context, everything - fetch them from the archived source file.

Step 1: Find the occurrence ID​

Open an issue's detail to list its occurrences:

GET /?api=error&id=<issue-id>

Each entry in the occurrences array carries its own id, plus byte_start, byte_end, and the source path. Pick the id of the occurrence you want to read.

Step 2: Fetch the raw bytes​

GET /?api=source&occurrence=<occurrence-id>

Log Lens opens the archived file, seeks to byte_start, and reads through to byte_end. The response is JSON:

FieldMeaning
contentThe exact bytes of the event
byte_start, byte_endOffsets read from the file
pathArchived source file the bytes came from
log_typeParser that produced the occurrence
channelLog channel, when known

The read is capped at 4 MiB. Occurrences are far smaller than that in practice, so you receive the whole event.

If the source is unavailable​

If the occurrence ID is unknown, or the archived file has been moved, deleted, or pruned, the request fails:

{ "error": "The archived source file is unavailable." }

Pruning the processed archive removes older source files, so very old occurrences may no longer be readable even though the issue still exists. The indexed message, stack, and context preview remain in the issue detail regardless.

Notes​

  • This is a plain GET, so no cross-origin check applies. If an API key is configured, send it as X-Log-Lens-Token or Authorization: Bearer.
  • content is the raw file slice - Log Lens does not normalize or trim it, so it matches the log on disk byte for byte.