Skip to content
ZentrixDataBridge
§P06ProductMonitoring

Every record that moved, and every one that did not.

Runs, per-record execution history, a structured log stream, four metric charts and alert rules — built in from the start, because it cannot be retrofitted.

Start buildingDocumentation
FIG P2.1Monitoring · where it sits
Log streamSample data
  • 14:02:11run started trigger=cron version=v5 environment=production
  • 14:02:11source read complete objects=1 records=1284 cursor=2026-09-26T13:47:10Z
  • 14:02:12transform applied fields=9 derived=1 coerced=2
  • 14:02:12validation failed rule=email_required reason_code=field_required action=quarantine
  • 14:02:12validation failed rule=email_required reason_code=field_required action=quarantine
  • 14:02:12destination write batch=13 mode=upsert key=external_id written=1282
§MMechanisms

How it works

Mechanisms, not promises.

  • 01

    The execution record is the unit of truth

    Every number in the product — dashboard counts, charts, usage metering — is derived from executions and execution records, so two screens can never disagree.

  • 02

    Per-record forensics

    For one record: the source payload, the transformed payload, the validation results, the destination response and every delivery attempt. This is the deepest thing the product does.

  • 03

    Errors grouped by type

    Forty-three identical validation failures are one problem, not forty-three. The dashboard groups by reason code and shows the retry state.

  • 04

    Re-run what failed

    Replay a whole run, or only its failed records. The 1,282 that succeeded are not reprocessed.

  • 05

    Alerts that reach your systems

    Threshold rules on error rate, a throughput floor and connector health, delivered by email or as a webhook into your own on-call tooling.

  • 06

    Restrained charts

    One-pixel step lines, dotted gridlines, percentile lines without bands, and a per-interval density strip. No fills, no gradients, no decoration.

§AAPI

In the API

The same thing, from a terminal.

bash
curl "https://api.zentrixquark.com/v1/logs?run=run_8f21b7e0&severity=warn" \  -H "Authorization: Bearer zx_sk_live_…" # → 200{  "data": [    { "ts": "2026-09-26T14:02:12.402Z", "severity": "WARN",      "record": "0f2a41", "reason_code": "field_required",      "message": "validation failed rule=email_required action=quarantine" }  ],  "has_more": false}
Run statuses
SUCCESS · RUNNING · PARTIAL · FAILED · QUEUED · CANCELLED
Log severities
DEBUG · INFO · WARN · ERROR · FATAL, each with a structured context object.
Filters
Time range, flow, run, record, severity and environment — all URL-encoded so a filtered view can be pasted into a ticket.
Retention
Configurable per plan, with payload capture switchable off per flow for sensitive data.
§NNext

Next

Connections
All product areas