Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Practical guide: building an admin UI to replay DLQ events
A concise guide to building an admin UI that inspects and replays failed webhook events from a DLQ in a secure and auditable way.
Quick answer
An admin UI for replaying DLQ events lets teams inspect failed webhook events and retry them in a controlled way. The UI should show error types, payloads, replay attempts and audit records. Key elements are filters, test replays, rollback options and strict access controls. These features give support and engineering teams in Zurich, Geneva or Lausanne a safe, traceable interface to handle retries.
Goal of a DLQ replay UI
The UI should help users examine failed events from a dead‑letter queue and retry them selectively. It exposes root causes, allows targeted retries, and produces audit trails for support and developers.
Core features and feature set
Essential features include: searchable lists with filters (date, event type, status), detail view showing payload and error, configurable retry parameters (backoff, max attempts), a test endpoint for safe replays, batch replay, ignore/mark options, and immutable audit logs with user identity.
Recommended UI flows
1) Overview: filters and key metrics (DLQ count, error categories). 2) Select: mark single or multiple events. 3) Validate: auto‑checks (schema, signature, destination availability). 4) Test replay: run a single test against a sandbox endpoint. 5) Production replay: manual confirmation to perform live replay. 6) Results: show status and link to audit record.
Security and compliance considerations
Access control is critical: role‑based permissions (read, test, replay, admin) and SSO (SAML/SCIM). Verify signatures and mask sensitive fields when showing payloads. Apply rate limits and quotas to protect recipient systems. Store audit logs immutably with user ID, timestamp and outcome for traceability and compliance in Swiss operations.
Error handling and monitoring
Display clear error classes (client, server, timeout). Move repeatedly failing events into a separate state after configurable retries. Add alerts for error spikes (email, Slack). Useful metrics: replay success rate, mean time to replay, top error causes.
Technical architecture and integrations
Backend should include an API layer, job queue and worker processes to perform replays. Use an append‑only event store and immutable audit records. Integrate with identity providers (SSO), observability tools (Prometheus, Grafana) and secure webhook endpoints. Keep replay logic in server components; the UI should only control and trigger actions.
Frequently asked questions
Who should have access to replay functions?
Limit access by role: support can read and test, integration engineers can replay, admins manage settings. Enforce SSO and role‑based policies.
How do I test a replay without risking production?
Use a sandbox endpoint or a test header that prevents side effects in production. Always run single‑event test replays first.
What if the destination keeps failing?
Move the event to a 'pending fix' state or a separate category. Notify the recipient team and record all attempts in the audit log.
What audit data should be stored?
At minimum: user id, timestamp, event id, replay parameters, response code and error. Store payload snapshots with sensitive fields masked.