Event Monitor

Event Monitor is the operational dashboard for the platform’s asynchronous message infrastructure. It aggregates outbox and inbox statistics across the portal and all connected microservices, highlights failed (dead-letter) events that require attention, and provides retry, delete, and purge actions to resolve processing failures. The dashboard refreshes automatically every 30 seconds.

System administrator access only. This page is available exclusively to system administrators. It is not accessible from the standard tenant portal.

Accessing the Page

• Route: /outbox
• Menu Path: Settings → Data & Monitoring → Event Monitor
• Primary audience: System administrators only. Accessed via the system admin login at system.portal.net — not the tenant portal.

What you can do here

• View aggregated outbox statistics (Pending, Processing, Completed, Dead Letters) across the portal and all registered microservices.
• View per-service outbox health in the Services table and navigate to the dead-letter list for any specific service.
• View inbox dead-letter statistics and per-service inbox health in the Inbox tab.
• Monitor email delivery statistics and failed email dead letters in the Emails tab.
• Retry individual dead-letter events to requeue them for processing.
• Retry all dead-letter events for a service in a single operation.
• Delete individual dead-letter events permanently.
• Purge all dead-letter events for a service in a single operation (destructive — requires confirmation).

Common tasks

1. Open Settings → Data & Monitoring → Event Monitor at system.portal.net.
2. Check the Outbox tab Summary card — if Dead Letters is above zero, investigate the affected service.
3. In the Services table, identify which service has dead letters and click View Dead Letters to open its dead-letter list.
4. Review the event type, error message, and retry count for each failed event.
5. If the root cause has been resolved, click Retry on individual events or Retry All for the entire queue.
6. If an event is permanently unprocessable, click Delete to remove it from the queue.
7. Use Purge All only when all dead letters for a service are safe to discard — the action is irreversible.

Notes

• Statistics are aggregated from all microservices that have outbox monitoring configured. Services without outbox configuration do not appear in the Services table.
• The dashboard polls every 30 seconds. The last-updated timestamp appears at the bottom of each Summary card.
• Dead-letter events shown in red indicate active failures. Resolving the underlying service or payload issue before retrying prevents re-failure.
• The Inbox tab operates on the same pattern as Outbox but tracks inbound message processing failures.
• The Emails tab shows statistics from the email delivery service and its dead-letter queue for messages that could not be delivered.

Dashboard Tabs

Outbox Tab

The Outbox tab is the default view. It contains two sections:

Summary Card

Displays aggregated event counts across all services:

Metric	Color	What it shows
Pending	Yellow	Events queued but not yet picked up for processing
Processing	Blue	Events currently being dispatched
Completed	Green	Events successfully processed and delivered
Dead Letters	Red (when > 0)	Events that failed all retry attempts and require operator action

A refresh button in the card header triggers an immediate data reload.

Services Table

Lists each microservice that has outbox monitoring enabled:

Column	Description
Service	Microservice display name
Pending	Pending event count for this service
Processing	In-process event count
Completed	Completed event count
Dead Letters	Failed event count; highlighted in red when above zero
Status	Healthy / Error indicator based on whether dead letters exist
Actions	View Dead Letters button — navigates to the dead-letter list scoped to that service

Dead Letter List

Clicking View Dead Letters for a service opens the dead-letter management page scoped to that service.

Column	Description
ID	Internal event identifier (truncated)
Event Type	The type of message that failed
Correlation ID	Correlation identifier for tracing across services
Retry Count	How many times the event has been retried
Last Error	The most recent error message
Created	When the event was first created
Actions	Retry, Delete buttons per row

Page-level actions: Retry All, Purge All (requires confirmation dialog). Pagination is 20 rows per page with previous/next navigation.

Inbox Tab

Follows the same structure as the Outbox tab but tracks inbound message processing failures. The Summary card shows aggregated inbox metrics and the Services table shows per-service inbox statistics.

Emails Tab

Dedicated view for the email delivery service:

• An Email Stats card shows the email dead-letter count and last-updated time.
• An Email Dead Letters table lists individual failed email messages with their error details and retry/delete row actions.

Resending Events

To reprocess a dead-letter event after resolving the root cause:

1. Locate the event in the dead-letter list.
2. Click Retry on the row. The event moves back to Pending status and is requeued.
3. Monitor the Summary card — the Dead Letters count should decrease and Pending/Processing should increase.
4. If the event fails again, it returns to the dead-letter list with an incremented retry count.

To reprocess all dead letters for a service, click Retry All in the page header. A confirmation dialog shows the total count before proceeding.

Related Pages

• Micro Services — service registry; verify all services are active before running retry operations
• Event Registry — catalog of registered event types and service subscriptions