Operations | Monitoring | ITSM | DevOps | Cloud

One of my initial surprises upon joining Catchpoint about five months ago was to do with how much confusion there is in the observability market. Every single vendor has almost the same message around ensuring a great digital experience for your customers or employees or both. Of course, these experiences are critical to get right, but for the most part many of these solutions, at best, help to ensure that sites are live and available, and that they are reachable by some users.

When you think of a network, what comes to mind? MySpace, Facebook, Instagram, TikTok… LinkedIn if you’re all business? No, no, no, not what I meant! Not social networks – IT networks. What comes to mind now? Switches? Access points? Firewalls? A score of ethernet cabling? For us too, the network symbolizes all the traditional things that Auvik helps IT teams around the world manage and monitor.

We often think of DDoS attacks as volumetric malicious traffic targeted against organizations that effectively take a service offline. Most frequently detected by anomalous behavior found in NetFlow, sFlow, IPFIX, and BGP data, what may not be well understood is how the DDoS mitigation works and how it’s possible to visualize the effectiveness of the mitigation during and after an attack.

For server administrators tasked with ensuring the reliable operation of their web applications, the thought of a lurking cyberattack can be one to lose sleep over. An attack on your system and the services you provide could render your web applications unresponsive. What’s worse, important information that depends on privacy and the careful storing of data is put at risk.

At first, the benefits of public cloud adoption are clearly recognisable: newfound agility through an all-you-can-eat and on demand buffet of services, platforms, and infrastructure. But without appropriate monitoring, guardrails and process changes, this can change fast. While the perception is that cloud offers unlimited scalability and lower costs by only charging for the resources you use, the truth is that customers pay for the resources they order, whether they use them or not.