Activity log
The Gateway records every call: a read, a write, a call to a connected service, and a call that was refused. You see them in Agents, Activity.
What you see for each call
- When it happened, to the second, and how long it took.
- Who made it: the agent or the program, the person who connected it, and the access level it had at that moment.
- Where it came from: MCP or the HTTP API, and the app or the SDK on the other end with its version.
- What it called: the tool, and for a connected service, the service and its tool.
- What it was about: the document, file or task, or the number of the ticket or issue. For a list, how many items came back and which.
- The result: ok, error or refused, with the error message.
Click a call to open it. Filter the log by agent, by kind (reads, writes, service calls) and by result, or go to a date.
What the log keeps, and what it does not
The log keeps what identifies a call: the numbers of records, codes such as a status, dates, and the names of the arguments.
The log does not keep the content of a call. It does not keep free text such as a search query, a note or the body of a document. It does not keep people’s data such as a name, a document number, an email or a phone number. It does not keep anything that is named like a secret.
Reads of outdated versions
When an agent reads a document or a file, Basement records the version it read. If the document changes later, the log marks that read as outdated, and Agents shows which agents work from an old version.
Who sees the log
Admins and owners see the calls of every agent and program. Other members see the calls of the keys they connected.
How long the log keeps a call
The log keeps 90 days of activity. When a full month is older than 90 days, Basement moves it to a compressed file: a .zip with a CSV sheet, one line for each call. Admins and owners download these files in Agents, Older activity.