Cross-industry
Application & infrastructure monitoring
The challenge
When you run dozens of business-critical applications for clients, "it stopped working on Friday" is not an acceptable way to find out. Generic uptime pingers see whether a URL answers - not whether last night's import ran, a job queue is draining, or a certificate expires next week.
What we did
We built Miton, our monitoring platform: agents and probes execute scheduled checks - HTTP endpoints, database queries, job-queue freshness, certificate expiry, disk and service state - and report into a central engine with thresholds, escalation and a live cockpit.
Alongside it we operate a full observability stack for every application we run: structured logging (Seq), error tracking (GlitchTip/Sentry), metrics dashboards (Grafana, Zabbix) and enriched health endpoints as a standard part of every deployment.
The outcome
- Every application we operate ships with monitoring and observability by default
- Failures are typically known and being fixed before users report them
- Checks cover business outcomes (did the import land?) - not just uptime
- One cockpit across client platforms, our own products and infrastructure
Facing something similar?
We're happy to share how we approached it - engineer to engineer.