Request logs & usage
Every request to a project's memory in the last 7 days, refused ones included, found by request id; and what the Usage page counts.
Request logs
Request logs, under Project in the console, lists every request to the project's memory in the last 7
days, newest first, refused ones included: a wrong key (401), a missing header (400) and a body that does
not fit the route (422) all show here. Only what describes a request is kept: request and response bodies are
not stored.
| Column | What it shows |
|---|---|
| Time (UTC) | When it arrived. |
| Route | The memory route, such as search or add, or mcp for an assistant's tool call. |
| App user | The X-Alexein-User it named. |
| Status | The answer, such as 200 OK or 401 Unauthorized. |
| ms | How long it took. |
| Key or app | The key's label from API keys, or the assistant that signed in. |
Select a row for the whole request: its request id (with a copy button), the project, what it spent, the app and the client. Open app user goes to that app user's page.
Keys by name
A request names the key it was made with by its label, such as backend-prod. A key you have revoked keeps its
name, marked (revoked), so a client still calling with it shows up: its requests are refused with 401 and
listed, such as 401 Unauthorized under Old backend (revoked). Rotate the key in that client.
Find one request
Every response from the memory API carries its id in the X-Request-Id header, and every error the console
shows ends with one. Paste it in Request id to find that request, whoever made it. The
errors page says how to send an id of your own.
Filters
Filter by Route, by Status (2xx, 4xx or 5xx), by App user, or by Request id, then select Apply. Clear shows everything again; Load older pages back through the 7 days.
The console's own requests
The console reads memory with a key of its own for each project, labelled Console: the pages you open, the playground and the app user pages. Those requests are left out of the log, so it shows your app's traffic. Tick Show the console's own requests to see them too. A key counts as the console's only if the console made it: no header a request sends can hide it from the log. The playground's searches count against your plan's retrievals; the console's other pages are free. See Plan limits.
Usage
Usage, under Project, shows the organisation's spend today and the last 30 days of the project, or of every project for Owners and Admins, per UTC day:
- Requests, Retrievals (searches; every other read is free) and Writes (adds) count requests. They leave out the console's own requests, so they count your app's traffic.
- Spend per day counts everything, the playground included, with chat's part of it and a line at the daily budget.
- Today: Spent today and Chat spent today, for the whole organisation. Owners and Admins can Change limits.
- This month: Events added this month, from connected apps and API adds, and Retrievals, for the whole organisation, against your plan. Past either, requests are refused until the 1st (UTC): see Plan limits.
Every cap on spend, the daily budget, chat's cap, premium models' share and the cost per turn, is set under Settings › Limits; each member's personal memory cap is the memory platform's, under My memory › Settings › Limits. Limits says what happens when one is reached.
When the day's budget is spent, every console page says so: Today's budget is spent. Search answers without its relevance check, new facts wait and the playground's chat stops until midnight UTC. Chat in the desktop app uses credits instead, so it goes on. Owners and Admins can Raise the budget from there.
When the console cannot load something
A page or action that fails says what happened, what to do next, and the request id, with Copy request id. Send that id to your Alexein contact if it keeps failing: it finds the request in the log.
Related
- Errors: every status and message.
- Limits: your plan's limits, the daily budget and what is refused when.
- Authentication & keys: labels, revoking and rotating keys.