Observability
Observability gives you full visibility into the operational health of your Zeotap workspace — every sync, journey, loader, store feed, identity graph run, and trait evaluation, whether it succeeded or failed.
Behind the scenes, Zeotap records a single stream of observability events: one record for each operational outcome across the platform. That stream feeds three independent sinks, so the same signal can be inspected in SQL, drive real-time alerts, and flow into your existing monitoring platform.
The Observability Event Stream
Every operational outcome becomes one observability event, capturing what happened, to which resource, whether it succeeded, and any relevant metrics (row counts, duration, rejected rows). Events are produced for:
- Sync runs (reverse ETL to destinations)
- Journey runs (orchestrations)
- Loader runs (inbound data pulls)
- Store feed refreshes
- Identity graph runs
- Trait evaluations
- Event delivery and contract activity from the Streams module
Both completions and failures are recorded, including runs that stall and are later detected as failed, and signals for consecutive failures and automatic pausing.
The Three Sinks
In-Warehouse Log
Every observability event is written to a table in your own data warehouse, so you can query your complete pipeline history with plain SQL — join it against your other data, build dashboards in your BI tool, or run ad-hoc investigations. This is on by default. See In-Warehouse Log.
Alerting
The same event stream drives configurable alert rules. When a rule’s condition is breached, an incident opens and notifications are dispatched to your channels (Slack, email, or a webhook). Incidents recover automatically on the next clean run. See the Alerting section.
External Export (OTLP)
Export metrics, logs, and traces to any OpenTelemetry-compatible monitoring platform — New Relic, Datadog, Grafana Cloud, Honeycomb, or a generic OTLP collector — so Zeotap’s operational health sits alongside the rest of your infrastructure in the tools your team already uses. See External Export (OTLP).
Next Steps
- In-Warehouse Log — Query your pipeline history in SQL
- External Export (OTLP) — Send telemetry to your monitoring platform
- New Relic Setup — Step-by-step OTLP export to New Relic
- Alerting — Rules, channels, and incidents