All ideas/devtools/Plataforma SaaS para gestión, monitoreo y análisis de notificaciones con historial, recibos de entrega y métricas de throttling.

GitHubB2Bdevtools

Plataforma SaaS para gestión, monitoreo y análisis de notificaciones con historial, recibos de entrega y métricas de throttling.

Scouted 6 hours ago

6.8/ 10

Overall score

Turn this signal into an edge

We help you build it, validate it, and get there first.

Go from idea to plan: who buys, what MVP to launch, how to validate it, and what to measure before spending months.

Extra context

Learn more about this idea

Get a clearer explanation of what the opportunity means, the current problem behind it, how this idea solves it, and the key concepts involved.

Score breakdown

Urgency8.0

Market size7.0

Feasibility7.0

Competition5.0

Pain point

Falta de observabilidad y analítica en el envío y entrega de notificaciones con throttling.

Who'd pay for this

Equipos de desarrollo y operaciones de empresas que envían notificaciones masivas o críticas a usuarios finales.

Source signal

"Notification throttling is implemented but has no observability. There is no log of what notifications were sent, no per-channel delivery receipt, and no analytics on throttle behavior."

Original post

[Wave 200pts] Build Notification History, Delivery Receipts, and Throttle Analytics Dashboard

Published: 6 hours ago

Repository: Nexacore-Org/NexaFx-js Author: portableDD ## Summary Notification throttling is implemented but has no observability. There is no log of what notifications were sent, no per-channel delivery receipt, and no analytics on throttle behavior. ## Acceptance Criteria - [ ] Every notification send creates a NotificationLog entry (type, channel, recipient, status, timestamp) - [ ] GET /admin/notifications/history supports filters: userId, type, channel, status, dateRange - [ ] GET /admin/notifications/analytics returns: volume by type, per-channel delivery rates, throttle flush counts - [ ] GET /admin/users/:id/notifications returns all notifications sent to a specific user - [ ] DeadLetterProcessor emits CRITICAL admin notification when any job is dead-lettered - [ ] NotificationLog auto-purged after 90 days by cron ## Key Files - `src/modules/notifications/entities/notification-log.entity.ts` - `src/modules/notifications/services/notification-log.service.ts` - `src/modules/notifications/controllers/admin-notifications.controller.ts` - `src/queue/dead-letter.processor.ts` — inject NotificationService, emit DLQ alert - `test/notification-history.e2e-spec.ts` ## Constraints - Log writes must be async — fire-and-forget pattern - Log entity stores type, recipient, and summary only — no full payload - Complexity: **High — 200 points**

View on github ↗