Event Explorer and filtering

Event Explorer is an Organization-scoped view of ingested Events and their Deliveries.

Filters

You can filter by:

• Project — narrow to resources in one Project.
• Source — narrow to a particular Source.
• Destination — find Events with a Delivery to a Destination.
• Event reference — DeadHook Event reference or upstream Event ID.
• Event status — in progress, delivered, partial, failed, canceled, or expired.
• Delivery status — delivered, scheduled, retry, dead letter, stopped, expired, and related states.
• HTTP result — success, redirect, client error, server error, or network failure.
• Time range — when DeadHook accepted the Event.
• Search — subject-like references and identifiers available in the UI.

Filters combine. A reference from another Organization is not visible and behaves as not found.

Reading an Event

The Event summary shows:

• the aggregate status across its Deliveries;
• counts for delivered, failed, pending, stopped, and expired Deliveries;
• total attempts;
• the Source and acceptance time.

Open the Event to see one row per Destination Delivery, including its status, last error, next attempt, stop state, and recent attempts. Inspect each Destination independently.

What Event Explorer does not show

• full response bodies unless response capture was enabled;
• raw payloads to users without Developer-or-higher permission;
• another Organization's resources, even if an ID is known;
• proof that a Destination committed its business transaction after returning 2xx.

Use the Event detail for attempts and the Dead Letter Queue for terminal failures.