Monitoring
Schema events
Read the feed of source schema changes, see how SQL Flow handled each one, and find the tables that need your review.
The Schemas page lists the schema changes (DDL) that agents detected on the tables your pipelines capture, from every source, and what SQL Flow did with each one: apply it on the target, or hold the table for your review. For how schema changes reach each target, see Schema changes.
Open it from Schemas in the top navigation.
Summary tiles
Four tiles sit above the feed:
| Tile | What it counts |
|---|---|
| Applied | Events SQL Flow carried to the target, such as auto-propagated. |
| Detected | Events SQL Flow noticed and didn't apply by itself, such as needs review. |
| Blocked | Events whose action starts with blocked. The figure turns red when it isn't zero. |
| Tracked tables | The number of tables all your pipelines capture. |
The first three count the events in the feed and follow the Filter by pipeline choice. They don't show whether a change is still waiting for you: use the pipeline's Schema review card for that.
Read the feed
Recent schema events has one row per event, newest first:
| Column | Meaning |
|---|---|
| When | How long ago the agent reported the event. |
| Table | The source table, with its schema. |
| Change | A chip for the kind of change, followed by the statement. |
| Action | What SQL Flow did. |
Select a row to open its pipeline.
Kinds of change
| Chip | Meaning |
|---|---|
| ADD COLUMN | A column was added. |
| DROP COLUMN | A column was dropped. |
| ALTER TYPE | A column's type, nullability or position changed. |
| RENAME COLUMN | A column was renamed. |
| INCOMPATIBLE | The capture no longer matches the source table, so it is blocked. The statement reads like Source schema changed for <table> (capture <instance>). The current capture no longer matches the source. Reload this table to resume. |
When one statement changes several things, the chip shows the most significant one. DROP COLUMN and ALTER TYPE chips are amber, because they can discard data or change what the target holds.
Actions
| Action | Meaning |
|---|---|
auto-propagated | SQL Flow applied the change on the target, in order with the data. Nothing for you to do. |
applied | SQL Flow confirmed that the change is on the target. |
blocked · source schema changed | The capture can't follow the change. Reload the table, as the statement says. |
needs review | SQL Flow didn't apply this change automatically, for example a rename or a type change. If the target can't make the change exactly, SQL Flow holds that table at the change while every other table keeps streaming. Open the pipeline and look for a Schema review card. See Held schema changes. |
A held table doesn't raise an alert. If a pipeline's source schema changes, check this page or the pipeline for a Schema review card.
Filter by pipeline
Choose a pipeline in Filter by pipeline to see its events only, or All pipelines to clear the filter. The filter is part of the page address, so you can share the filtered view. The same events are on the pipeline's Schema tab, under Schema changes.
How long events are kept
Schema events are deleted after 14 days.
