---
title: Pipeline
description: The per-tenant activity view at
---

# Pipeline



## Purpose

PIPELINE confirms that the selected tenant's cameras are live and detections are flowing. It is an activity view: the camera list is derived from alert activity, not from the camera registry.

Deep link: `ops.useargus.co/#/pipeline` (nav group MONITOR).

## What it shows

* A "Selected tenant" line (or a pointer back to the TENANTS tab when none is picked).
* One card per camera with recent alert activity:
  * A status dot derived from the age of the last alert: under 5 minutes, under 60 minutes, or idle.
  * The camera id and a relative last-alert time.
  * Key-value rows: last alert timestamp, alerts in the last hour, alerts in the last 24 hours.

Data source: `GET /pipeline/health`.

## Actions

None. This view is read-only.

## Matching CLI

```bash
argusctl traffic
argusctl status
```

`argusctl traffic` reports detection and incident throughput per camera and per tenant; `argusctl status` is the one-screen overview. See [diagnostics commands](/docs/cli/diagnostics) and [core commands](/docs/cli/core).

## Notes

* Polled on the 15 second timer with in-place repaint; the last good data stays on screen if a refresh fails.
* Because this view is built from alert activity, a registered, streaming camera with no alerts in the window does not appear here. The empty state says so explicitly: "no alert activity in the last 24h" and points to [Cameras](/docs/console/cameras) for the full registry and stream health.


---

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)