---
title: Logs
description: The remote-support audit feed at
---

# Logs



## Purpose

LOGS is the first-class place to read the remote-support audit trail for the selected tenant: activations, commands, arm and disarm, enroll and revoke events. It also points to the other log surfaces (live agent tails, Sentry, Render).

Deep link: `ops.useargus.co/#/logs` (nav group REMOTE SUPPORT).

## What it shows

* REMOTE-SUPPORT AUDIT: up to 200 events from the last 7 days for the selected tenant. Columns: TIME, EVENT (a chip, color-coded for success-like and failure-like event types), OPERATOR, AGENT, COMMAND, RESULT (the result summary or an error code).
* OTHER LOG SOURCES: a static card explaining where the other logs live. Live per-agent log tails appear on the AGENTS view (each agent's last-known log tail in telemetry); for a fresh live tail you run `argusctl support command --cmd tail_log` from a tailnet machine, because commands are gated off the browser by design. The card links out to SENTRY, the RENDER ops-api logs, and the AGENTS view.

Data source: `GET /support/audit?tenant_id=...&limit=200`.

## Actions

None on the audit table itself; the OTHER LOG SOURCES card contains navigation links only.

## Matching CLI

```bash
argusctl logs tail --since 1h --actor user_ABC --json
argusctl support command <tenant> --session <tok> --command tail_log --args '{"lines":200}'
```

`argusctl logs tail` reads the platform audit log; the `support command` form pulls a live log tail from an agent during a gated session. See [argusctl logs](/docs/cli/logs) and [argusctl support](/docs/cli/support).

## Notes

* Requires a selected tenant. With none selected the page shows "No tenant selected" and points to the TENANTS tab.
* Polled on the 15 second timer with in-place repaint.
* Empty state: "no remote-support activity for this tenant".


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)