Skip to content
sistemo.io beta

Activity log

A read-only record of every action on your account: what happened, who did it, and when. Available on every tier.

curl -sS https://api.sistemo.io/v1/activity \
  -H "Authorization: Bearer $SISTEMO_API_KEY"
{
  "activity": [
    { "action": "machine.stopped", "actor": "system:spend_guard",
      "machine_id": "123e4567-e89b-12d3-a456-426614174000",
      "metadata": {}, "created_at": "2026-09-22T13:36:30.452270Z" },
    { "action": "exec", "actor": "user",
      "machine_id": "123e4567-e89b-12d3-a456-426614174000",
      "metadata": { "exit_code": 0, "timeout_sec": 30 },
      "created_at": "2026-09-22T12:15:04.118233Z" }
  ],
  "total": 2,
  "next_cursor": ""
}

The first entry is the useful kind: the machine was stopped, and not by you. The spend guard stopped it because the balance hit €0. Your own logs cannot show that, because your client never made the call.

What is recorded

Metadata only. Never script text, never output. An exec entry stores the exit code and the timeout you asked for — there is no field for the script, so nothing can add one later. Each action has a fixed set of keys, checked by a test.

If you need to know what a script did, log that yourself.

Recorded Not recorded
Action, actor, timestamp, machine id Script text, stdout, stderr
Exit code and timeout of an exec CPU, memory or network metrics
Volume and snapshot ids, disk sizes Names you chose for them

Actors

actor Means
user You, via the API or dashboard
system:spend_guard Balance hit €0; your machine was stopped
system:reclaimer Grace window expired; resources were deleted

In the dashboard

Activity in the sidebar is the account-wide feed, with search, type filters and a date range. Each machine also has an Activity tab.

Limits

Retention 365 days
Scope needed read or full
Export None — page it out yourself with the API
Cost Free

A machine's entries outlive the machine, including its machine.destroyed entry. Deleting your account deletes them.