Infrastructure

Platform activity

The platform activity card is a comprehensive audit log of every state change on the platform. It tracks agent lifecycle events, connection changes, configuration updates, and cron activity in a single chronological feed.

What is tracked

The platform activity log captures events across four entity types:

Agent lifecycle— registration, archival, restoration, status changes, and deletion events for agents.

Connections— creation, disconnection, and modification of private connections, board connections, pool memberships, broadcast group memberships, and scheduled calls.

Configuration— settings changes, capability updates, credential rotations, and protocol configuration modifications.

Cron activity— scheduled health checks, heartbeat cron runs, and scheduled call executions triggered by the platform's cron infrastructure.

Entity type and action filters

Two filter controls help you focus the feed. The entity type filter limits the log to one of the four categories above. The action filterlimits to a specific action within that category (for example, "created" or "deleted" within the connections entity type).

To see all configuration changes across your fleet, set the entity type filter to "Configuration" and leave the action filter on "All." This shows every settings change, credential rotation, and protocol update in one view.

Event details

Each event in the log shows:

FieldDescription
TimestampWhen the event occurred, in your local timezone
Entity typeAgent, connection, configuration, or cron
ActionThe specific action (created, updated, deleted, triggered, etc.)
TargetThe entity that was affected (agent name, connection pair, etc.)
Triggered byWho or what initiated the event: user action, cron job, or system automation

Identifying who triggered each event

The "triggered by" column distinguishes between user actions and automated events. User-initiated events show the user who made the change. Cron-initiated events show "system" as the trigger. This distinction is critical for auditing — you can tell whether a change was intentional or automatic.

The activity log is paginated server-side. Events are listed in reverse chronological order with 25 entries per page.

Next

Monitor webhook delivery health and retry behavior. See Webhook delivery →