Monitoring product architecturePublic engineering build

Argus Monitor

A monitoring SaaS architecture with services, queues, WebSockets, CI tests, PostgreSQL, Redis, and resilient external integrations.

Argus MonitorPublic build

Dashboard & APIAuthenticated configuration and live status flows.

Event pipelineIndexers and adapters normalize external data into queued work.

Alert deliveryRules, notifications, and state records complete the loop.

ReactNestJSPostgreSQLRedisPrismaBullMQSocket.io

Built forProduct teams building real-time monitoring systems

My roleCreator and full-stack infrastructure engineer

StatusPublic product architecture; no usage or uptime claims

Problem

Event monitoring needs dependable ingestion, rule evaluation, live state, notification delivery, and explicit failure handling.

What shipped

Service boundaries for API, indexing, adapters, alerts, and notifications.

Redis/BullMQ queues and WebSocket updates for background and live work.

Unit, integration, and Playwright flows around core boundaries.

System shape

01
Dashboard & API
Authenticated configuration and live status flows.
02
Event pipeline
Indexers and adapters normalize external data into queued work.
03
Alert delivery
Rules, notifications, and state records complete the loop.

Evidence

Public service architectureDocumented test postureResilience and secret controls

Tools & interfaces

ReactNestJSPostgreSQLRedisPrismaBullMQSocket.ioPlaywright

Next honest step