> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/administration/audit-and-status-logs.md).

# Audit & Status Logs

The **Status & Logs** screen (shown in the navigation as *Audit & Status Logs*) gives you a live view of the operational state of all your pipelines in one place, updated in real time.

![The Status & Logs screen showing four summary cards: Pipelines (6, with 0 healthy, 6 degraded, 0 failed per the card counters), Last 24H Success (100.0%, 284 succeeded, 0 failed), DLQ Depth (0), and Avg Run Duration (7s across 264 runs in the last 24 hours). A green "All pipelines healthy" banner appears below the cards. The Pipelines section lists six connector pipelines — Bamboo, GitHub, Okta, Slack, WorkDay, and AOH Test AD — each showing an OK status badge, with last-run and sync-count details. Filter buttons (All, Failed, Partial, OK) are visible.](/files/EL5KNFBBashtUA1E9vBR)

*The Status & Logs screen, live-refreshed. The summary cards give an at-a-glance read of overall pipeline health.*

## Summary cards

| Card                 | What it shows                                                                                               |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Pipelines**        | Total number of pipelines, broken down by healthy, degraded, and failed                                     |
| **Last 24H Success** | Percentage of runs that succeeded in the last 24 hours, with raw succeeded and failed counts                |
| **DLQ Depth**        | The number of items waiting to be reprocessed — a non-zero value may indicate a problem worth investigating |
| **Avg Run Duration** | Average time per run across all pipelines in the last 24 hours                                              |

## Pipelines list

Below the summary cards, each active pipeline is listed as a tile. Each tile shows:

* **Pipeline name** — the Connector feeding into AOH Sync (for example, "Bamboo → AOH Sync")
* **Status badge** — **OK**, **Partial**, or **Failed**
* **Last run** and **records synced** count

Use the **Filter** buttons (**All**, **Failed**, **Partial**, **OK**) to narrow the list to pipelines in a particular state.

{% hint style="info" %}
The screen header shows **Live · refreshed Xs ago**, confirming data is current. No manual refresh is needed during normal monitoring.
{% endhint %}

## What to do when a pipeline shows a problem

{% stepper %}
{% step %}
**Identify the affected pipeline**

Use the **Failed** or **Partial** filter to isolate pipelines that are not fully healthy. Note the pipeline name and last-run timestamp.
{% endstep %}

{% step %}
**Check the DLQ Depth card**

A depth greater than zero means records are queued for reprocessing. If the depth is growing, investigate the corresponding Connector.
{% endstep %}

{% step %}
**Review the Connector**

Navigate to the [Connectors](/feature-reference/connectors.md) section, open the relevant Connector, and check its sync history for error details.
{% endstep %}

{% step %}
**Contact support if needed**

If the issue persists, gather the pipeline name, last-run time, and any error messages, then open a support request.
{% endstep %}
{% endstepper %}

## The audit trail: decisions, not just changes

AOH Sync records more than state changes — it records reviewed decisions too. When an orphaned account is dismissed, when an anomaly is acknowledged, or when a machine identity ownership transfer occurs, the action and the person who took it are logged. This means "we knew and decided" is never confused with "we never noticed": both deliberate choices and automated changes appear as attributable entries.

## Related

* [Connectors — Sync History](/feature-reference/connectors/logs.md) — per-Connector run logs and error details
* [System Settings](/administration/system-settings.md) — event health summary over the last 30 days
* [Action Center](/feature-reference/data-quality.md) — review and resolve data quality issues flagged during syncs
* [Roles & Permissions](/core-concepts/roles-and-permissions.md) — how access changes are authorized and recorded


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aohwv.dev/administration/audit-and-status-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.