How do I see Monetize logs, retries and the DLQ?
Every forwarded meter event is logged with timestamp, destination, payload, HTTP response, and retry count. Failed events are visible in the Retries tab while they're being retried, and in the DLQ tab once they exhaust the retry budget. From the DLQ you can inspect the error, fix the root cause, and replay events one by one or in bulk.
Three views
- Logs — delivered events with full request/response, filterable by destination, assistant, and end-user.
- Retries — events currently being retried; shows next attempt time and last error.
- DLQ — events that exhausted retries; inspect, fix, and replay individually or in bulk.
Common errors
- 401 from Stripe: restricted key is wrong or revoked. Issue a new one and replay.
- 404 meter not found: meter was deleted. Recreate it in Stripe (or point the destination at a new meter) and replay.
- customer not found: the end-user mapping returns a missing
cus_xxx. Update your JWT or assistant config and replay.
Alerts
DLQ depth is surfaced on the Monetize overview tile. We send a workspace-admin email when the DLQ exceeds 100 entries in any 1-hour window so silent metering failures don't go unnoticed.
Next steps
FAQ
- How long are logs retained?
- 30 days for delivered events, 90 days for DLQ entries.
- Can I replay an entire batch?
- Yes. Select multiple DLQ rows and click Replay. Each event is re-enqueued with a fresh retry budget.
- Do replayed events double-bill?
- No. Each event keeps its original identifier and Stripe deduplicates by identifier.