Skip to content
Monitoring and uptime

Somebody is watching, and it is not you

The worst way to find out your till is down is a phone call from a queue. Managed Cloud checks your service continuously and raises a human the moment something stops answering.

In short

  • Checked continuously
  • Alerts reach a person
  • Performance watched
  • Expiry watched
What the service does

Monitoring and uptime

Availability is checked continuously. If something stops responding, an alert reaches a person who is already working on it before your first customer of the day notices.

Continuous availability checks

Your service is polled around the clock, including the hours nobody on your team is awake. That is what monitoring means, and there is no version of it that runs office hours only.

Alerts that reach a human

An alert that lands on a screen nobody is looking at has done nothing. Ours reach an on-call person with the context to act on them.

Slow counts as broken

We watch response times, not just whether the service answers at all. A till that takes eight seconds to ring an item is down as far as your queue is concerned.

Certificate and renewal expiry

Dates that quietly lapse are monitored the same way availability is, so a certificate or a domain never expires because a calendar entry was missed.

Capacity watched over time

Growth is a trend before it is an incident. We watch storage and load so we can act early rather than after a bad Saturday.

You can see it too

The portal shows current status and recent history for your own account, so you are never asking us whether it is just you.

In scope

What is monitored

Not just a single ping at a home page.

  • Service availability, checked continuously from outside your network
  • Response times, so degradation is caught before an outage
  • Background jobs and scheduled tasks, which fail quietly if nobody looks
  • Backup completion, because a backup that did not run is worth nothing
  • Certificate and domain expiry dates
  • Storage and load trends, watched for growth rather than only for failure
How it works

What happens when something breaks

The order matters. You should hear from us before you hear from a customer.

  1. The check fails and an alert is raised

    Not a log entry. An alert to an on-call person, with enough context to know which customer and which service is affected.

  2. We start work and we tell you

    You are contacted rather than left to notice. Being told there is a problem and that it is being handled is most of what a customer needs in the first ten minutes.

  3. We close it out with an explanation

    When it is resolved you get a plain account of what happened, what we changed, and what stops it recurring. No jargon and no blame shifting.

The point of it

What your team never has to do

  • Discover an outage from a customer standing at the counter
  • Guess whether it is the internet, the till, or the software
  • Chase someone for an update while the shop is closed
  • Wonder whether last night's scheduled job ran at all
Questions

Asked and answered

If yours is not here, ask us directly. We would rather have the conversation than have you guess.

Any figure we commit to belongs in your service level agreement, where it is a contractual term rather than marketing. Ask us for the current agreement and we will send it before you sign anything.

You will be told. Contacting you is part of the response, not an optional extra we get to if there is time.

No, and no managed service can. We monitor the service we run. If your branch loses connectivity, that is between you and your provider, though we will happily help you work out which side the problem is on.

Yes. The dashboard in your portal shows current status, recent checks and your last backup, so you have the same picture we do.

See the whole service

This is one part of Managed Cloud. The rest of it works the same way: our team does the work, and your team gets on with trading.