Skip to content

Merging master back into develop to send changes downstream after one-off release #2228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 1, 2021
Merged

Merging master back into develop to send changes downstream after one-off release #2228

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d7ad3e0
Removed public beta flag
forstisabella Nov 30, 2021
ca86749
Merge pull request #2217 from segmentio/develop
pwseg Nov 30, 2021
86304f0
Merge branch 'master' into remove-data-lakes-beta-flag
forstisabella Dec 1, 2021
68abe35
Merge pull request #2211 from segmentio/remove-data-lakes-beta-flag
forstisabella Dec 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions src/connections/storage/data-lakes/sync-history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,6 @@ title: Data Lakes Sync History and Health

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.

> info ""
> 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.

## Sync History
The 'Sync History' table shows detailed information about the latest 100 syncs to the data lake. The table includes the following fields:
* **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
Expand Down