Operations | Monitoring | ITSM | DevOps | Cloud

As we were planning “Cloud Atlas,” our primary goal was to talk with someone who was “in the room” during the genesis of the cloud. Allan Vermeulen, who worked for Amazon from 1999-2021, and who proposed Amazon Simple Storage Service (S3), became that source. Allan is a born engineer. He has always enjoyed building things — whether “out of bits and software or boards and lumber,” Allan takes pleasure in creating useful things.

Communication carries more weight than ever before. Businesses are so much more connected to their customers given the number of mediums they can communicate through; Twitter, Instagram, Facebook, and even TikTok. Because of this, it's essential to prioritize these lines of communication throughout your day-to-day. Some might even say that over-communicating is the best way forward. Why? No one likes a company that appears simply like a black box with zero insight into what's happening.

True observability requires visibility into both the application and network layers. For companies reliant on multi-zonal cloud networks, the days of NetOps existing as a team siloed away from application developers are over.

Our aim, like always, is to help users thrive. We want them to receive real value from all that we deliver through our various features. And it’s equally important to offer flexibility by providing all different ways to use those features. This way, you’re free to use the feature in the way that's most convenient. Driving this vision of ours, well, forward, we have now extended our Logs Forwarding experience from CLI to within the Console.

To provide proper visibility into the health and status of your systems, observability tools require access to the internal and external services you’re using, and Sensu is no different. In the past, this could mean exposing sensitive authentication credentials like usernames and passwords with local environment variables or even by including the secret information in your monitoring configuration.

Ready, set, go: when it comes to customer service, it's a race against the clock. Customers expect lightning-fast responses and complete solutions to their problems. But what happens when your help desk can't keep up with the pace? The answer is simple: frustration, dissatisfaction, and potentially lost clients. That's why measuring and improving Time to Resolution (TTR) is crucial. As a customer, there's nothing more irritating than dealing with a slow or ineffective help desk.

The average cost of an IT outage is $12,900—per minute. And when it comes to a “significant outage,” organizations reported the average overall cost was a whopping $1,477,800. On the latest podcast episode of That’s great IT, I spoke with Scott Lee, AVP for infrastructure and ITOps at Arch Mortgage Insurance Company, part of Arch Capital Group, about how organizations can best navigate IT outages.

Are you tired of constantly experiencing buffering, lagging streams, or dropped calls? Have you ever wished you had a network watchdog to monitor your connection and alert you of any issues before they become a major headache? Well, you're in luck because we have just the tools and tips for you! In this step-by-step guide, we'll show you how to become a network watchdog yourself and use Network Monitoring tools to monitor your network connectivity like a pro.

Nothing is certain in this world except for death, taxes, and that you will eventually run out of disk space. You may have used our unique predict operator to query logs and forecast future values (we’ve even heard of customers predicting their ingest volume for Sumo Logic log data to better forecast their usage and budget!) — and wanted to do the same with metrics. With the recent general availability of the predict for metrics operator, you can.

The process of building and maintaining modern, cloud-based applications requires a new approach to infrastructure monitoring. Traditionally, engineers would try to isolate a specific infrastructure component causing an issue — and fix it alone, without diving into code. Today, DevOps engineers must understand how application performance is related to their infrastructure. Infrastructure, for DevOps engineers, is an enabler to deploy code.