Skip to content

Commit b2a7852

Browse files
committed
DOC-359 Copyediting pass
[netlify-build]
1 parent 7040edb commit b2a7852

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

src/connections/storage/data-lakes/sync-history.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -3,49 +3,49 @@ title: Data Lakes Sync History and Health
33
---
44
{% include content/plan-grid.md name="data-lakes" %}
55

6-
The Segment Data Lakes sync history and health tabs generate reports about data syncs so you can monitor the health and performance of your data lakes. These tools provide monitoring and debugging capabilities within the Data Lakes UI, so you can identify and proactively address data sync or data pipeline failures in real time.
6+
The Segment Data Lakes sync history and health tabs generate real-time information about data syncs so you can monitor the health and performance of your data lakes. These tools provide monitoring and debugging capabilities within the Data Lakes UI, so you can identify and proactively address data sync or data pipeline failures.
77

88
> info ""
99
> This feature is currently in Public Beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern the use of this feature.
1010
11-
## Sync history
12-
The sync history table shows detailed information about the 100 most recent syncs to the data lake. The sync history table includes the following fields:
13-
* **Sync status:** The status of the sync: either 'Success,' where all rows synced correctly, 'Partial Success,' indicating some rows synced correctly, or 'Failed,' where no rows synced correctly
11+
## Sync History
12+
The 'Sync History' table shows detailed information about the latest 100 syncs to the data lake. The table includes the following fields:
13+
* **Sync status:** The status of the sync: either 'Success,' indicating that all rows synced correctly, 'Partial Success,' indicating that some rows synced correctly, or 'Failed,' indicating that no rows synced correctly
1414
* **Start time:** The time the sync began
1515
* **Duration:** How long the sync took to complete
16-
* **Synced rows:** The number of rows that were synced to the data lake
16+
* **Synced rows:** The number of rows that synced to the data lake
1717
* **Notices:** Any notes or warnings about the sync
1818

19-
Selecting a row in the sync history table opens a sidebar showing the number of rows that were synced in each collection.
19+
Selecting a row in the Sync History table opens a sidebar showing the number of rows from each collection that synced.
2020

21-
To access the sync history page from the Segment app, open the **My Destinations** page and select the data lake. On the data lakes settings page, select the **Sync History** tab.
22-
23-
> note ""
24-
> Users cannot select when syncs occur. Syncs occur approximately every two hours.
21+
To access the Sync History page from the Segment app, open the **My Destinations** page and select the data lake. On the data lakes Settings page, select the **Sync History** tab.
2522

2623
## Health
2724
The health tab provides an overview of the rows that synced to your data lake both today and each day for the last 30 days.
2825

29-
The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection were synced, and the percentage of all synced rows that each collection represents.
26+
The bar chart, 'Daily Synced Rows,' shows an overview of the rows synced for each of the last 30 days. Hovering over a date shows the number of rows that were synced for that day. Selecting a date from the bar chart opens the Daily Row Volume table, which provides a breakdown of which collections synced, how many rows from each collection synced, and the percentage of all synced rows from each collection .
3027

3128
The Daily Row Volume table contains the following information:
32-
* **Collections:** The name for each collection of properties synced to the data lake
29+
* **Collections:** The name of each collection of properties synced to the data lake
3330
* **Rows:** The number of rows synced from each collection
3431
* **% of Total:** The percentage of the total number of rows synced that each collection represents
3532

36-
Above the Daily Row Volume table is an overview of the total syncs for the day, showing the number of rows synced, the number of collections that synced, and the date.
33+
Above the Daily Row Volume table is an overview of the total syncs for the current day, showing the number of rows synced, the number of collections that synced, and the current date.
3734

3835
To access the Sync history page from the Segment app, open the **My Destinations** page and select the data lake. On the data lakes settings page, select the **Health** tab.
3936

4037
## Data Lakes Reports FAQ
4138
##### How long is a data point available?
42-
The health tab shows an aggregate view of the last 30 days worth of data, while the sync history retains only the last 100 syncs.
39+
The health tab shows an aggregate view of the last 30 days worth of data, while the sync history retains the last 100 syncs.
4340

4441
##### How do sync history and health compare?
45-
The sync history feature shows detailed information about the most recent 100 syncs to a data lake, while the health tab shows just the volume of rows synced to the data lake over the last 30 days.
42+
The sync history feature shows detailed information about the most recent 100 syncs to a data lake, while the health tab shows just the number of rows synced to the data lake over the last 30 days.
4643

4744
##### What timezone is the time and date information in?
4845
All dates and times on the sync history and health pages are in the user's local time.
4946

5047
##### When does the data update?
51-
The sync data for both reports updates in real time.
48+
The sync data for both reports updates in real time.
49+
50+
##### When do syncs occur?
51+
Syncs occur approximately every two hours. Users cannot choose how frequently the data lake syncs.

0 commit comments

Comments
 (0)