You hear about a problem from us, not from your users
We watch uptime, errors, disks and certificates. When something happens, we respond and tell you what happened and what we did.
What happens when monitoring spots something
Example: a full disk on a server.
- 1DetectionMonitoring checks the app from outside, reads error logs and watches server resources.
- 2AlertA crossed threshold or a new kind of error sends an alert to someone on our team.
- 3ResponseWe remove the cause or limit the damage before users notice anything.
- 4UpdateYou get a short message on what happened, what we did and whether anything needs a permanent change.
Signs nobody is watching the app
A customer reports the outage
The certificate expired
The app slows down quietly
Backups don't work
What we watch
The scope is agreed at the start, depending on the app and infrastructure.
Uptime
Errors
Performance
Resources
Certificates and domains
Backups
How we check the results
Every month we show uptime, incidents and who noticed them first.
- 1Uptime this month
- 2Incidents caught by monitoring
- 3Incidents reported by users
- 4Time to response
The goal is for the second number to be bigger than the third.
Common questions
Do you monitor at night and at weekends?
Monitoring runs all the time. The scope of response outside working hours goes into the contract.
Do you need server access?
For full monitoring, yes. We can check uptime from outside without access.
Who gets the alerts?
Our team, and we tell the person you name about important incidents.
Will monitoring slow the app down?
Not noticeably. The tools collect data in the background and are chosen to fit your infrastructure.
Describe your application
Tell us what the app is, where it runs and how you find out about outages today. We reply within one business day.