> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/monitoring/job-status/cdc-sources/monitoring-v1.md).

# Monitoring- V1

The **Monitoring** tab provides insight into the status of your CDC job, from job level, through to individual tables within the replication. The metadata updates in real time, ensuring you have the latest information possible about the status of your job:

<figure><img src="/files/tizyMjRkC0aRnCmMO1Bx" alt=""><figcaption><p>Monitor each table within your replication job to see the synchronization progress.</p></figcaption></figure>

### Job header

In the top left-hand corner of the tab is the name of your job, along with the status, e.g. **Running**, and color-coded icon to alert you to any errors or warnings so you can take appropriate action. If your job has an error, the error message is displayed across the top of the tab

In the top right corner, the tab displays the source and target where the job ingests the data from and to. The source includes the frequency of the extract, e.g. **Extract every 1 minute**, and the target includes the frequency of the load, or how often data is written, e.g. **Load every 6 hours**.&#x20;

Click on the three-dots menu to show the options to **Pause Load to Target**, or **Drop Job**. Each option opens a modal dialog asking you to confirm your selection.

***

### Overview

The following information is available for your job:

* **Binlog Delay**: the duration passed since the last time a change was read from the binlog. Reading from the binlog is performed every minute.
* **Changes Read Until**: the date and time when the changes were last read from the binlog.
* **Replicated Tables**: the number of tables being replicated.
* **Replication Status**: the current status of the table replication. A table can be in one of the following states:
  * **Pending Snapshot**: the number and percentage of tables in the replication that are pending snapshot.
  * **Snapshotting**: the number and percentage of tables in the replication that are currently being snapshotted by the job.&#x20;
  * **Syncing**: the number and percentage of tables in the replication that have been snapshot and are now synchronizing between source and target.

***

### Replication table

The replication table displays the status of each table within the replication. Use the search box to display a subset of tables, or click on the **Filters** icon to filter the table results by **Replication Status**, **Load State**, and/or **Has Errors**.

<table><thead><tr><th width="228">Column</th><th>Description</th></tr></thead><tbody><tr><td>Target Schema</td><td>The target schema where the data is loaded.</td></tr><tr><td>Target Table</td><td>The name of the target table in the destination.</td></tr><tr><td>Replication Status</td><td>The current status of the data load, e.g. <strong>Pending snapshot</strong>, <strong>Snapshotting</strong>, or <strong>Syncing</strong>. </td></tr><tr><td>Changes Loaded Until</td><td>The point in time that the last changes from the source table were successfully loaded into the target database. The date signifies the last synchronization point and indicates the data's status in the target table, reflecting the time up to which it is synced with changes made in the source table.</td></tr><tr><td>Pending Changes</td><td>The number of changes extracted from the binlog that have not been loaded to the target yet.</td></tr><tr><td>Load State</td><td>The status of the task loading the changes to the target, performed according to the interval defined when creating the job. Displays the status, e.g. <strong>Succeeded</strong> or <strong>Failed</strong>, alongside the datetime stamp when the data will next load.</td></tr><tr><td>Error</td><td>The latest error encountered while processing the table's data. </td></tr></tbody></table>


---

# 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://upsolver.gitbook.io/content/reference-1/monitoring/job-status/cdc-sources/monitoring-v1.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.