Propose checks, monitor table health, investigate anomalies, and reduce alert noise.
A Scout is a persistent agent attached to one table. It moves through intake, evidence, investigation, report, and delivery.
Open a catalog table, select Scout, review the proposed checks, and choose Arm. Inferred activation proposes no more than 12 checks. Manual mode supports explicit freshness, volume, completeness, uniqueness, and custom SQL requirements.
New workspaces can arm five Scouts by default. Disabling one releases its active capacity.
embrasure monitor scouts list --connector YOUR_CONNECTOR_ID
embrasure monitor scouts get SCOUT_ID
embrasure monitor scouts arm SCOUT_ID --yes
embrasure monitor scouts run SCOUT_ID --yes
embrasure monitor scouts disable SCOUT_ID --yes| Check | Detects |
|---|---|
| Freshness | Late or missing delivery. |
| Row count | Unexpected volume. |
| Null rate | Completeness changes. |
| Cardinality | Distinct-count changes. |
| Metric band | Numeric aggregates outside a learned range. |
| Uniqueness | Duplicate identifiers. |
| Value composition | Categorical mix drift. |
| Domain | Values outside an allowed set. |
| Referential | Keys that no longer resolve. |
| Schema and contracts | Type, shape, regex, range, or custom SQL violations. |
Scout uses robust median, seasonal, trend, and distribution models where they fit the signal. Use manual thresholds when the expected boundary is already known.
Scout separates observed evidence from inference. A hypothesis moves through proposed, testing, supported, ruled out, confirmed, or likely states. Missing permission or source access blocks evaluation instead of becoming a false healthy result.
embrasure investigate table catalog.schema.orders \
--detail-level full \
--direction bothMCP clients can call investigate_table for the same bounded catalog, lineage, change, trust, and health context.
embrasure monitor tables mute MONITOR_ID --limit 120 --yes
embrasure monitor tables unmute MONITOR_ID --yes