Skip to main content

Notification Dashboard Integration

Summary​

The executive dashboard reads three notification sources and renders three KPI tiles plus a quick-action link. All three sources come from the extracted service.

Audience​

Engineers, QA, support, administrators, product owners and architects.

Reference Content​

The verified reference material for this topic is set out in the sections below.

Sources read​

SourcePath shapeCap
Notification statisticsStatistics endpoint—
Failed notificationsFailed queue25
Notification auditAudit query50

Each is fetched through a wrapper that labels the source and tolerates failure, and all dashboard sources are awaited together. A failing notification source degrades its tiles rather than the whole dashboard.

Metrics derived​

Three values are computed from the statistics payload using a tolerant field lookup that accepts several possible field names:

TileDerivation
Failed notificationsFailed count from statistics, falling back to the length of the failed list
DeliveredFirst match among delivered, sent or success fields
PendingPending field

Verified contract mismatch. The extracted statistics endpoint returns counts named templates, recipients, messages, sent, failed, read, processed events and delivery attempts. It returns no delivered field and no pending field.

The delivered tile therefore resolves through its sent alias and does render. The pending tile has no matching field at all and resolves to undefined, so it renders permanently in the unavailable state. The tolerant lookup is what prevents this from being an error — it degrades silently.

Rendering​

The failed tile is rendered with a danger tone and links to the operations console. Delivered and pending render in a secondary grid, also linking to the console. Every tile passes an unavailable flag derived from its value being undefined, so a missing metric renders as unavailable rather than as zero — an important distinction for anyone reading the dashboard.

A quick-action entry links to the Notification Center alongside other operational destinations.

What the dashboard does not show​

No per-channel breakdown, no delivery-rate trend, no time series, no tenant dimension, no retry-success rate and no broker or consumer health. The statistics endpoint supplies none of these, and the dashboard adds no aggregation of its own.

Classification​

Partial — tiles are Implemented; one of the three renders permanently unavailable against the current contract.

Requires confirmation​

Whether the statistics contract should add delivered and pending counts, or the dashboard should drop the pending tile, requires confirmation.

See Also​

Keywords​

  • Notification database
  • Dashboard Integration
  • Draft database documentation

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/dashboard/dashboardApi.ts
  • UI/salary-ui/apps/client-hrms-portal/src/dashboard/DashboardPages.tsx
  • microservices/src/notification-service/Api/NotificationEndpoints.cs

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-21
  • Review cycle: Quarterly