Docs and articles

R-75

Technology

Tessera DB Tutorial: Monitor Sync Attempts Across All Sources

Every sync attempt — success or failure — is recorded with its timing and cursor. Use the cross-source feed to see your whole fleet at once.

PAR2 Labs

August 29, 2026

2 min

Tessera DB Tutorial: Monitor Sync Attempts Across All Sources

Tessera records every sync attempt across every source. Per-source history is one click away; cross-source activity is its own view.

01

Before you start

Tier

01

Connectors and their sync monitoring are an Enterprise feature.

02

Step 1: Per-source history

In the Data Sources view, open the history panel on any source. It shows the recent sync attempts with each one's timestamp, rows imported, duration, the new cursor value, and the error message if it failed.

03

Step 2: Cross-source feed

The sync-activity view collects every sync from every source, newest first, in one place. Filter by source or by status to focus on failures. A summary strip shows totals — how many syncs ran, how many failed, how many rows came in, across how many sources — for a "how is the fleet doing today" glance.

Filter by source or by status to focus on failures.

04

Step 3: Feed it into your monitoring stack

Tessera emits standards-based metrics in Prometheus and OpenTelemetry formats, so the same signals flow into Grafana, Datadog, Honeycomb, or any OTLP backend — no lock-in. Alert on repeated failures or unexpected zero-row syncs there.

05

What the history captures

Timestamp of the sync attempt.

Rows imported (zero if nothing new, or on failure).

How long the attempt took.

Error message on failure; none on success.

New cursor value, for incremental syncs.

06

What the history captures — how much is kept

The panel keeps the most recent attempts per source; older ones roll off.

Key Takeaways

01

Opened a source's history panel to see each attempt's timestamp, rows imported, duration, cursor value and any error.

02

Used the cross-source sync-activity view, filtered by source or status, with its summary strip of totals.

03

Sent the same signals to your monitoring stack as Prometheus and OpenTelemetry metrics.


PAR2 Labs · Technology

Talk to us

One copy of the data, five ways to read it.