Nidopr Monitor

A custom observability console for the Nidopr platform. One installable app watches the whole business, classifies who’s visiting, and pushes alerts straight to a phone. I built it and run it as part of operating Nidopr in production. No third-party monitoring vendor, no per-host billing, no lock-in.

Problem

A production system with a scraping layer, an ML pricing model, a public app, and dozens of unattended nightly jobs has a lot of surfaces that can fail quietly. Off-the-shelf monitoring means stitching together vendors and paying per host or per metric. It still misses the business-specific things that matter, like whether a search returned results, or whether last night’s data refresh completed. I wanted one place to see all of it, owned outright.

Build

A self-hosted observability layer purpose-built for the platform:

• 40 automated production health checks covering the live surfaces of the business, not just generic infra pings.
• Installable PWA that runs on desktop and on a Galaxy Fold, so the console travels in a pocket.
• Three alert sinks: Discord, email, and web-push directly to the phone, so a failure reaches a person wherever they are.
• Visitor analytics with bot / human / internal classification. This separates prospective users from crawlers and my own traffic, so the numbers mean something.
• A search → view → contact behavior funnel to see where users drop off.
• A self-healing client that recovers on its own instead of going dark.

Numbers

• 40 health checks running against production.
• 3 independent alert channels (Discord, email, web-push to phone).
• Visitor traffic split three ways: bot / human / internal.
• A profiled endpoint taken from 4.8s to 0.1s, a 48× speedup, found and fixed using the console’s own instrumentation.

That last one is why the tool exists. The observability layer didn’t just report a slow endpoint. It gave me the visibility to locate the fix and confirm it worked.

Stack

Installable PWA (desktop + Galaxy Fold) · web-push notifications · Discord and email alert sinks · self-hosted visitor analytics with bot/human/internal classification · a search-to-contact behavior funnel · a self-healing client · endpoint performance profiling. Part of the Nidopr platform, operated in production.