> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request Log Dashboards

> How to use StackOne's Log endpoints to build admin or customer-facing request log dashboards

Embed StackOne request logs in your own product UI — an internal operations dashboard for your team, or a scoped log viewer for your customers. This guide covers the endpoint call order for each pattern.

<Info>
  This guide covers **request logs** only — the same data shown on the [Request Logs](/guides/request-logs) dashboard page. For the full endpoint hierarchy, see [Request Log Debugging](/api/request-logs-debugging). To export logs into Grafana, Datadog, or a data warehouse, see [Observability & Log Sync](/api/observability-sync).
</Info>

The API follows the same drill-down hierarchy as the StackOne dashboard: **list → detail → advanced / steps / defender**.

***

## Admin operations dashboard

Build an internal dashboard for your team to monitor integration health across all linked accounts.

### Call order

1. **Summary metrics** — [Get Logs Stats Aggregate](/platform/api-reference/logs/get-logs-stats-aggregate) for error counts, latency percentiles, and request volume.
2. **Breakdown** — [Get Logs Stats Dimensions](/platform/api-reference/logs/get-logs-stats-dimensions) to group by connector, account, or status.
3. **Activity table** — [List Logs](/platform/api-reference/logs/list-logs) with time-range and connector filters.
4. **Row drill-down** — [Get Action Log](/platform/api-reference/logs/get-action-log) using `action_run_id` from the selected row.
5. **Deeper inspection** — On demand, call steps, advanced, or defender endpoints based on what the operator needs to see.

```mermaid theme={null}
sequenceDiagram
    participant Dashboard as Admin Dashboard
    participant StackOne as StackOne Logs API

    Dashboard->>StackOne: POST /logs/stats/aggregate
    StackOne-->>Dashboard: KPIs (error rate, p95 latency)

    Dashboard->>StackOne: POST /logs (filtered, paginated)
    StackOne-->>Dashboard: Log rows with action_run_id

    Note over Dashboard,StackOne: Operator clicks a failed row

    Dashboard->>StackOne: GET /logs/actions/{actionRunId}
    StackOne-->>Dashboard: Request detail

    opt Needs request/response bodies
        Dashboard->>StackOne: GET /logs/actions/{actionRunId}/advanced
        StackOne-->>Dashboard: Full payloads
    end
```

***

## Customer-facing log viewer

Expose a scoped log viewer inside your product so each customer sees only their own integration activity.

### Call order

1. **Resolve the linked account** — Map the signed-in end-user to a StackOne `account_id`.
2. **List logs** — [List Logs](/platform/api-reference/logs/list-logs) with `filter.account_ids` set to that account.
3. **Show summary in the table** — Display `event_time`, `action_id`, `connector_key`, `status_code`, `duration_ms`, and `success` from list results. Do not fetch advanced logs for every row.
4. **Detail on demand** — [Get Action Log](/platform/api-reference/logs/get-action-log) when the user opens a specific entry.

<Tip>
  Scope every list request to a single `account_id`. Your backend should hold the StackOne API key and enforce account scoping server-side — never expose project-wide logs to end-users.
</Tip>

### Key fields for the log table

| Field         | Source                   |
| ------------- | ------------------------ |
| Timestamp     | `event_time`             |
| What ran      | `action_id`              |
| Connector     | `connector_key`          |
| Outcome       | `success`, `status_code` |
| Duration      | `duration_ms`            |
| Drill-down ID | `action_run_id`          |

***

## Related

<CardGroup cols={2}>
  <Card title="Request Log Debugging" icon="bug" href="/api/request-logs-debugging">
    Debug failed action calls and trace execution steps
  </Card>

  <Card title="Observability & Log Sync" icon="chart-line" href="/api/observability-sync">
    Sync logs to Grafana, Datadog, or custom pipelines
  </Card>

  <Card title="Request Logs (Dashboard)" icon="scroll" href="/guides/request-logs">
    View and filter logs in the StackOne dashboard
  </Card>

  <Card title="List Logs API" icon="code" href="/platform/api-reference/logs/list-logs">
    List request logs endpoint reference
  </Card>
</CardGroup>