Operations | Monitoring | ITSM | DevOps | Cloud

One of the best things about cloud computing is how it converts technical efficiencies into cost-savings. Some of those efficiencies are just part of the tool kit, like pay-per-use Lambda jobs. Good DevOps brings a lot of savings to the cloud, as well. It can smooth out high-friction state management challenges. Sprucing up how you provision cloud services, for example, speeds up deployments. That’s where treating infrastructure the same as workflows from the rest of your codebase comes in.

All deployments are not created equal, but you'd never know it from your Slack channel notifications. In reality, some deployments you really care about, as they contain things like API changes or database migrations, and you want that information to surface. We created tags in Sleuth for this very reason. Out of the box, Sleuth matches files in your deployment with known patterns, and if any are found, tags your deployments automatically.

Once upon a time the telephone system was a trusted method of connecting people. While we now spend more time on our phones than ever, our relationship to phone calls has changed -- we’re hesitant to answer calls from unknown phone numbers, often because we think the call is a con. But what if the caller ID is spoofed/modified and made to look like a telephone number that you may trust or a number with a local area code and familiar prefix?

Hybrid cloud infrastructures run critical business resources and are subject to some of the strictest network security controls. Irrespective of the industry and resource types, these controls broadly fall into three categories. Workloads (pods) running on Kubernetes are ephemeral in nature, and IP-based controls are no longer effective. The challenge is to enforce the organizational security controls on the workloads and Kubernetes nodes themselves.

Errors and bugs are a nightmare for any software engineer or developer. Even though errors can seem like a bad experience for any developer or website owner, errors can help improve the quality of a website. You may be wondering, “But how?” Errors pinpoint the weaker parts of the website, giving you direction of what to work on.

Tuesday morning you roll out of bed, turn off your alarm, tiptoe down the stairs, retrieve your paper, flip the hallway lights on, feed the dog, and start making coffee—in five minutes. Performing this series of early-morning tasks is called chunking. Certain neurons in the brain “bookend” the habit for you, signaling the routine has started (the alarm) and ended (coffee).

The community forum is a place where you can meet and chat with other Icinga users. It’s hosted by Icinga and moderated by both the Icinga team and members of the community. It’s mostly being used as a platform to ask and answer technical questions about Icinga, which is a great way to learn more about the tool stack! What does it look like? It’s a discourse platform, so it’s a collection of threads or topics which are open for anyone to leave a comment on!

Some time ago, an ex-colleague of mine at DAZN received an alert through PagerDuty. There was a spike in error rate for one of the Lambda functions his team looks after. He jumped onto the AWS console right away and confirmed that there was indeed a problem. The next logical step was to check the logs to see what the problem was. But he found nothing. And so began an hour-long ghost hunt to find clues as to what was failing and why there were no error messages.

Chief Architect at Drift, Freedom Dumalo, recently spoke with the CloudZero team about how they’ve successfully cut cloud costs by $2.4M in just a few months. When the world rapidly transitioned to work from home, Drift, the conversational marketing platform known for their chatbots, saw a spike in their customer utilization. The largest usage spike were among new users experimenting with their free trial. This increase in engagement was a great sign for their business.