It's 8:40 on a Monday and reception is already calling you. Email won't send. The label printer in the warehouse is sitting there. The EFTPOS machine has that look. Someone is on hold to the internet provider, and someone else is telling customers you'll ring them back. You found out because a person got stuck. Nobody's system told you first.
That's a normal morning for a lot of Perth offices, and it eats the day. Watching the network is how you hear about the fault earlier, while there's still time to do something. What you want is a person who sees it and acts. A login to a screen full of green ticks, on its own, doesn't help the person at reception.
What usually falls over
In a small business the "network" is a handful of boxes that the day depends on. The internet link. The firewall, which is the box that joins you to that link and keeps the guest Wi-Fi away from the tills. The wireless points, especially the one at the far end of a shed. The server or little file box everyone saves to. And the backup that was supposed to run last night.
Those fail in boring ways. The NBN drops for twenty minutes and comes back, then does it again at lunch. A disk fills up on the file server over a few weeks. A backup job has been failing since someone changed a password and nobody noticed. One wireless box dies and half the warehouse decides "the Wi-Fi is just bad here." None of that needs a specialist to understand. It needs someone looking, on a normal Tuesday, before it becomes the thing reception rings you about.
If you've got a second site, a yard in Welshpool and an office in Osborne Park for example, add the link between them. And if the business lives in Microsoft 365, you still have a local network. When the firewall is off, the cloud is on the other side of a dead line.
What is worth watching
You don't need an alert every time a laptop goes to sleep. That trains everyone to ignore the inbox. Start with the things that stop the business, and ignore the rest until you've lived with it for a fortnight and you know what "normal" looks like.
- Is the internet link up, and has it bounced several times this morning? A flapping line and a dying modem feel the same to staff. They're different jobs.
- Is the firewall reachable, and is its licence still current? Some of them keep passing traffic after the subscription lapses, and quietly stop getting updates.
- Are the switches and wireless points alive? One dead box in an aisle is a "Wi-Fi is rubbish" complaint with a simple cause.
- Is the server or file box running out of disk, or complaining about a drive? Disks usually grumble before they take the files with them.
- Did last night's backup finish? A job that has been failing for three weeks won't save you. We've written about what a useful backup actually looks like if you want to go further than the green tick.
Add the public website only if orders or enquiries depend on it. The check can be humble. Does the homepage answer, and is the little padlock still in date? You don't need a second product for that.
Someone has to act on it
The failure we see most often isn't "no monitoring." It's monitoring that emails a shared inbox everyone assumes someone else reads. Or a tool the last IT person installed, still running, with the alerts going to an address that left with them. Ask it in plain English. When the internet at the office drops at 8:40 on a Tuesday, who is told, how, and what do they do in the first little while?
A useful response is boring and specific. The alert names the site and the box. Someone checks it is real, not a two-minute blip. If the whole office is dark, they look at the carrier before they start changing settings. If it's one server, they work on that. They tell a person at your place what staff should do in the meantime, even if the message is "use phones as hotspots for mail, and stop retrying the file server." Silence, while three people poke cables, is how a small fault becomes a morning of conflicting stories.
Be honest about hours. A bakery and a law firm don't have the same "after hours." Write down when a fault actually costs you money. If the contract says 24 hours and the reality is "we look at email in the morning," you don't have overnight cover. You have a slogan. Plenty of businesses are fine with faults handled through the working day, as long as that's what was agreed. This sits naturally inside managed IT, next to the help desk, rather than as a gadget you bolt on and forget. If you're still only ringing someone once it's already broken, we've talked about the point where that stops fitting.
The gear has to be something we can see
A modem from the supermarket is fine in a house. It usually can't tell us much, and it can't keep the guest Wi-Fi away from the tills. Business firewalls, switches and wireless that can be logged into remotely are what make the watching real. If today's kit can't do that, the honest answer is a planned swap, not a promise that software will invent a view the hardware doesn't have.
The same goes for passwords. If the only login to the firewall is on a sticky note, or the last provider won't hand it over, we can't see the fault from here. Part of taking a network on is getting those logins into a place the business controls, and changing them so an ex-supplier can't still get in. That's the difference between a remote fix and a drive across the city to press a button.
What to ask before you sign
You don't need the longest feature list. You need a short set of checks that match how your day falls apart, and a named way those checks turn into action. These questions flush that out:
- Which boxes will you watch in the first month, by name?
- Who gets a serious alert, and what happens during our working hours?
- What do you deliberately not alert on?
- How do we see that the backup finished, and when was a restore last tried?
- What happens to the history and the logins if we part ways?
If the answer is a slide about clever software and nobody can say who picks up the phone, keep looking. Our network monitoring sits inside Our One Plan, for clients who want the security work alongside it. It isn't a dashboard we leave you logged into. If that's the wrong shape, we'll say so.
Questions we get asked
Is this just antivirus with a fancier name?
Antivirus looks after the PC in front of someone. Monitoring is how you find out the internet, the server, or last night's backup has fallen over. You want both. They do different jobs.
We're only a small office. Is this over the top?
If the day stops when the internet or the server stops, it isn't over the top. You can start with the internet link, the firewall, the main server or file box, and whether the backup actually finished. You don't need a wall of graphs.
Will this stop us needing someone on site?
A lot of faults can be seen and fixed from our end, if the gear allows it. A dead switch in a cupboard, a cable, or a wireless box on the warehouse wall still needs a person in the room. The useful part is knowing which one it is before anyone drives across Perth.
What if we only want someone during office hours?
Then say that. Plenty of Perth businesses don't need a night shift. They need faults seen while people are at work, and a clear way to reach someone if a Saturday really would cost them. Don't pay for a 24 hour promise you won't use.
If you want a second look
If the last outage is still fresh, tell us what happened and who found out first. We'll say whether watching the network would have changed that morning, or whether the real gap is somewhere else. No slide deck required.
Call 08 6146 2410 or email info@strideit.com.au. If you'd rather read how it fits with the rest of the work, the network monitoring page is the short version.