Logs

Logs is in the sidebar for everyone. Only owners and admins can read it. Members see "Only admins and owners can see logs." See Roles.

The header

The line under the title spells the range out.

Pick a range

• Presets count back from the moment the list was read, not from midnight.
• Future dates cannot be picked. An end before the start reads "Pick an end date on or after the start."
• Selecting a bar on the volume chart also sets a custom range. The menu then reads Custom range.

Live updates

The list reads up to a fixed moment, so paging holds still while new events arrive.

The pill counts up to 100 and then reads 100+ new events. Refresh and the pill both move the list, the chart and the counts up to now.

Filters

Each filter takes one value. Clear resets every filter and any custom range, and keeps the preset.

The volume chart

The card above the list shows how many events match, like 1,204 events, and 24 bars across the range.

• Hover a bar for its time span and count.
• Select a bar to narrow the range to that slice.
• A count that hit the reading cap carries a plus, and the tooltips say "at least".
• The card folds away when nothing matches.

The list

Events run newest first, in one band per day. Each band names the day and counts the rows loaded for it. The list loads 100 events at a time. Load older events reads the next page.

A row reads left to right. The status dot, the area icon, the event label, the summary and a pill for anything but success come first. Who did it, what it used, one number and the time follow.

Entries do not expire. Once the range reaches the first entry, the foot of the list reads History starts and the date.

Folded rows

Three or more entries of the same event in a row fold into one line, like 5 Tool calls.

• The line names what the entries were about, like the tools called.
• It counts how the entries went. For billed work it also shows their total usage and cost.
• Its dot takes the worst outcome, so one failure inside shows red.
• A run broken by another event becomes two runs.
• Folding is off while a Type filter or a search is set.

Opening a folded line shows the outcome counts, the time span, a Usage total for billed work, and Entries. An entry opens in its place with Back to 5 tool calls.

An entry

Press a row to open its drawer. The title is the event label.

Only this person, beside a teammate under By, narrows the list to that teammate.

Billed rows show tokens, emails or pages, and their cost. View all under Recent usage in Settings → Billing opens Logs with Usage on. Plans and prices are on Billing.

Share a view

Every filter, the range and the open entry live in the URL. Copy the address to share the view.

https://median.sh/logs?range=7d&category=tools&outcome=failed

A shared link reads up to the moment it is opened.

Export

Export saves every event that matches the filters and range, not only the rows loaded.

• Files are named like median-logs-2026-09-26.csv.
• While it runs, the button reads like Exporting 1,200….
• One export reads up to 500 pages of 200 events. With a search, a Done by filter or two filters at once, a page can hold fewer matches, so the export can reach that limit with far fewer events. Past it the export fails with "Too many events to export at once. Narrow the range and try again."
• If paging stalls, it fails with "The export stopped partway. Try again."
• A failure shows an Export failed callout with the reason.

What is logged

Events sit in the areas the Type filter lists.

An AI run shows what it was for instead of its event label, like Sentiment check or Analytics question.

What is never logged

• Page views, reads and opened settings, including reading this page
• API requests that succeed, and API refusals other than rate limits
• Background work that succeeded
• Prompts, model answers and model names
• What customers wrote, and their names and email addresses. Entries link conversations and customers by ID and name them when opened.

Summaries and errors are one line of up to 300 characters. Anything shaped like a secret reads [hidden]. A URL keeps only its scheme and host.

Explore from Logs

Explore opens the explorer on the Activity log, counted per day and split by outcome, over every day the range touches. Its samples are "Failed events by area", "Credits used by AI feature, per day" and "Slowest tools". Queries, datasets and charts are on Analytics.

Over the API, CLI and MCP

Owners and admins can read the log from outside the app.

• GET /v1/logs takes from, to, search, category, outcome, actorKind, actorId, conversationId and usage=true. The range defaults to the last 30 days.
• Pages hold up to 200 entries, default 100. Keep snapshot fixed across pages. A page can come back short, or empty, before isDone is true.
• GET /v1/logs/{id} returns the entry, what it touched, and up to 50 entries about the same conversation.

median logs list --category tools --outcome failed

curl "https://api.median.sh/v1/logs?category=tools&outcome=failed" \
  -H "Authorization: Bearer $MEDIAN_KEY"

Every flag is in the CLI reference.