Skip to main content
Real-Time Event Streams are in private beta. Contact your Mixpanel account team to enable the feature for your project.
Every Sync and Destination has an explicit state that is visible without opening the detail view. This page is the reference for what each state means, how state transitions are logged, and which metrics you can use to monitor health.

​
Sync states

Sync state is shown as a status badge on the Syncs list view.
When a Sync is disabled, events matching the filter are discarded. Mixpanel does not accumulate a backlog to replay when the Sync is re-enabled.

​
Destination states

Destination-level state (separate from Sync state) is a Phase 2 feature. During the private beta, authentication status is visible on the Destination card, but the full Destination state model below reflects the target design.
Authentication failures on delivery immediately flip the Destination to auth_error — the failure is never silently swallowed. Re-authenticating updates the existing Destination in place; you do not need to delete and recreate it. See Webhook authentication.

​
Audit logging

All state changes are audit-logged with a timestamp and the acting user. Use the audit log to trace who paused a Sync, when credentials were rotated, or when a Destination first tripped into auth_error.

​
Observability panel

The full observability panel is a P1 requirement scheduled to land before GA. Some metrics may be limited or presented differently during the private beta.
Each Sync has a dedicated metrics view for monitoring delivery health.

​
Metrics

  • Events delivered — counts over the last 1 hour, 24 hours, and 7 days.
  • Delivery success rate — percentage of events that received a 2xx response within the retry window.
  • Events failed after max retries — count, with retained payload samples and destination response.
  • Pending retry queue depth — number of events currently waiting in the retry queue.
  • p95 delivery latency estimate — end-to-end latency from ingestion to a confirmed 2xx response.
  • Webhook URL domains — the destination domains this Sync is delivering to.
Metrics refresh approximately every 5 minutes. A health indicator on the Syncs list view reflects the current error state without a page load.
  • Alert on error and auth_error. These states indicate customer action is required and will not self-heal.
  • Watch unhealthy early. It often precedes error and gives you time to investigate before events start hitting the failed events log.
  • Track failed events during rollouts. After changing your endpoint or payload template, check the failed events log for 4xx errors before assuming success.
  • Review audit log entries. Especially when a Sync unexpectedly stops streaming — it may have been disabled by another admin.

Delivery and reliability

Retry policy, failed events log, and at-least-once delivery.

Set up a Sync

Create a Destination and configure a webhook Sync.