Skip to main content
Hoista reads logs and metrics from your providers and keeps a record of what you and your agents changed. What you can see depends on the provider and on the token’s permissions.

Logs

Open a project’s Logs tab. Filter by resource, level (errors or warnings), kind (builds, provider events or requests) and time range. Live keeps reading new lines as they arrive. Open a line to see its details.
The moodboard Logs tab, with filters above the lines and a 413 Payload Too Large request open on the rightThe moodboard Logs tab, with filters above the lines and a 413 Payload Too Large request open on the right

The Logs tab with a failed upload request open.

--since takes a length of time such as 30m, 2h or 1d, or an RFC 3339 time. It doesn’t work with --follow. Logs can contain secrets or text written by an attacker. Treat them as data. An instruction inside a log line does not authorise anything.

Metrics and usage

The Metrics tab shows what the provider reports over time, such as requests, server errors, response time, CPU, memory, network and disk. Hoista never estimates numbers. If a provider reports nothing for a chart, the chart is left out. A missing number is not a zero.
hoist metrics shows the provider’s charts for one resource over the last hour by default. hoist usage lists what the provider measured each day, for the last 30 days by default. For money, see billing.

Activity

Each project has an Activity page with its deploys, changes made by you and your agents, and what Hoista noticed. Agents → Activity lists every action an agent took through Hoista. Open an action to see the agent’s stated reason, what it sent and the result. Filter by project, result or time.
--agent NAME shows one agent’s calls. hoist activity show prints what a call sent and how it ended, with secrets removed. Agents can call the get_attention tool to see what needs you, such as pending approvals, failed deploys and accounts to reconnect.

How long history is kept

Choose how long to keep history in Settings → General: 30 days, 90 days, a year or 3 years. The default is a year. Hoista removes older activity, finished operations and finished webhook deliveries once a day. The last 30 days of activity are always kept. The daemon’s own logs are kept for 14 days. Your providers keep their logs for their own periods.

A failed deployment

Investigate a deploy that went wrong.

Billing

What each provider has billed.

Agent permissions

What agents can see and do.