Log details

One log entry and the full request flow it belongs to.

Where: Logs → Logs → entry · /projects/<project>/logging/logs/<logId>

Opening an entry does more than show that one row: the page loads every entry that shares its correlation id and renders them as a vertical timeline, oldest first — so the whole flow (HTTP request → queries / commands / handlers → end) is visible on one screen.

Screenshot TODO — capture comes from testing-plan area 18-logs-ui.

What you see

• Request flow summary — how many entries share this flow, and the Correlation Id with a copy button. An entry without a correlation id is shown on its own.

• Timeline nodes — one per entry, tagged by kind from the event code prefix: HTTP (http:*), Query (query:*), Command (command:*), Handler (handler:*, trigger:*, webhook:*), or plain Log. Warning and error entries get amber / red icons so problems stand out.

• Collapsed, a node shows one line: title, timestamp (UTC), Level, Module, and Event. Click it to expand the full detail inline: the message, Trace / Span ids when present, and the Metadata tree — the structured payload grouped into http, request, response, … sections.

• The entry you clicked in the list starts expanded, highlighted, and marked Selected.

Back to logs returns to the list with your filters and page position intact.

Use it from code

Logs → Audit (getLogsByCorrelationId).

API reference

Endpoints: Get Logs By Correlation Id, Get Logs.