You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cloud/managing-airbyte-cloud/review-connection-status.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ products: all
6
6
7
7
Each connection you've set up in your Workspace has a **Status** page that displays the connection's current status, timing of the next scheduled sync, and a summary of historic sync trends. Reviewing this page allows you to monitor the health of your connection.
Copy file name to clipboardExpand all lines: docs/cloud/managing-airbyte-cloud/review-connection-timeline.md
+20-11
Original file line number
Diff line number
Diff line change
@@ -2,27 +2,36 @@
2
2
products: all
3
3
---
4
4
5
-
# Review the sync history
5
+
# Review the connection timeline
6
6
7
-
The job history displays information about synced data, such as the amount of data moved, the number of records read and committed, and the total sync time. Reviewing this summary can help you monitor the sync performance and identify any potential issues.
7
+
The Connection Timeline displays information about several types of relevant connection events. The following events are included in the Connection Timeline:
To review the Connection Timeline, click a connection in the list and navigate to the "Timeline" tab to view its event history. The page displays recent events and their statuses. Where relevant, the event will also show the user who took the action.
10
16
11
-
To review the sync history, click a connection in the list and navigate to the "Job History" tab to view its sync history. The page displays recent syncs and their statuses. The sync status is defined as:
17
+
18
+
19
+
## Sync, Refresh, and Clear events
20
+
21
+
Completed Syncs, [Refreshes](/operator-guides/refreshes), and [Clears](/operator-guides/clear) will have a status associated to the event.
| Succeeded | 100% of the data has been extracted and loaded to the destination |
16
-
|Partially Succeeded |A subset of the data has been loaded to the destination |
17
-
| Failed |None of the data has been loaded to the destination |
18
-
| Cancelled | The sync was cancelled manually before finishing |
26
+
|Incomplete | The sync encountered an error, and should resolve itself. A subset or none of the data has been loaded to the destination.|
27
+
| Failed |The sync encountered a fatal error, and needs user intervention to resolve. A subset or none of the data has been loaded to the destination.|
28
+
| Cancelled | The sync was cancelled manually before finishing.|
19
29
| Running | The sync is currently running |
20
30
21
-
If you have recently run a [refresh](/operator-guides/refreshes) or [clear](/operator-guides/clear), you will also see this noted on the Job History page and their corresponding status.
22
31
23
-
## Sync summary
32
+
Airbyte will also separately record when a sync has been manually started by a user.
24
33
25
-
Each sync shows the time the sync was initiated and additional metadata. This information can help in understanding sync performance over time.
34
+
For sync and refresh events, Airbyte also shows the volume of synced data, such as the amount of data moved, the number of records read and committed, and the total sync time. Reviewing this timeline can help you monitor the connection and identify any potential issues.
@@ -31,7 +40,7 @@ Each sync shows the time the sync was initiated and additional metadata. This in
31
40
| x loaded records | Number of records the destination confirmed it received. |
32
41
| xh xm xs | Total time (hours, minutes, seconds) for the sync to complete |
33
42
34
-
While most syncs only contain a single attempt, a sync can sometimes fail. In the event of a failure, Airbyte will make several attempts to sync your data before waiting for the next sync to retry. You can read more about our retry approach [here](../../understanding-airbyte/jobs.md#retry-rules).
43
+
While most syncs only contain a single attempt, a sync can sometimes fail. In the event of a failure, Airbyte will make several attempts to sync your data before waiting for the next sync to retry. You can read more about our retry approach [here](../../understanding-airbyte/jobs.md#retry-rules). If multiple attempts are used in a sync, you can open the logs to see individual logs from each attempt.
35
44
36
45
Airbyte summarizes metrics in the sync summary across all the attempts in the sync. As a result, you may observe that the number of records extracted is higher than the number of records loaded if an attempt fails during the extraction process. A successful sync status means that all the records from the source have been successfully written to the destination.
Copy file name to clipboardExpand all lines: docs/using-airbyte/getting-started/set-up-a-connection.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Once you've set up all the connection settings, click "Set up connection". You'v
42
42
43
43
Once you've finished setting up the connection, you will be automatically redirected to a connection overview containing all the tools you need to keep track of your connection.
0 commit comments