Operations | Monitoring | ITSM | DevOps | Cloud

Hello, Checkly community and Monitoring as Code (MaC) aficionados! We have some exhilarating news that we can't wait to share. Our mascot is sporting sunglasses today because Checkly has been named in Gartner®'s 2023 Cool Vendors in Monitoring and Observability: Where Awareness Meets Understanding report!

Vydia is dedicated to helping creators gain more control over their audio and video content with a centralized tool for distributing, managing, protecting, and optimizing AV files. Vydia’s software team describes themselves as a “DevOps team first and foremost” delivering new features and updates in a tight loop. They are always in search of new ways to improve and modernize the development process.

Last week, our CTO, Todd Kesselman, presented on "Driving AWS Infrastructure Insights into Kafka" in downtown Vancouver, Canada. In his presentation, he revealed an unobtrusive way to share a wide range of operational information between organizations in a way that can easily be incorporated into your event pipeline. The featured technology is the AWS Event Bus. To clarify, the Event Bus is a message bus that enables multiple AWS accounts to publish and receive events to and from each other.

This week Intel released a statement regarding Microarchitectural Data Sampling (MDS), another vulnerability in the "speculative execution" feature of modern processors. This is for HyperThreading and is the feature that allows the CPU to work out what commands will be run next, if they would affect the current running command and if not, run it on the same core.

Infrastructure as code is an important methodology for ensuring that your distributed systems are treated as cattle and not pets. Your Kubernetes and Rancher clusters are no different. You should be able to provision your Rancher clusters, your Kubernetes clusters, and all of your apps with automation.

Back in 2017, I wrote a post titled “3 pro tips for Developers working with Kinesis streams”, in which I explained why you should avoid hot streams with many Lambda subscribers. When you have five or more functions subscribed to a Kinesis stream you will start to notice lots of ReadProvisionedThroughputExceeded errors in CloudWatch.

Imagine you are driving a car on a freeway. Your speedometer is telling you you’re going 62 mph. But you “gotta go fast”. Faster than then 65 mph speed limit. So you go for it: first 68mph, then 75mph, then 80mph. Then you pass a police officer hiding in a speed trap. To your dismay, they pull you over and give you a ticket. All is not lost: there is a silver lining here.

Find out why Cloudsmith thinks Puppet is one seriously classy company., why brand equity is important, and what impact a dot com has.

AKS is the managed service from Azure for Kubernetes. When you create an AKS cluster, Azure creates and operates the Kubernetes control plane for you at no cost. The only thing you do as a user is to say how many worker nodes you’d like, plus other configurations we’ll see in this post. So, with that in mind, how can you improve the AKS cluster performance of a service in which Azure pretty much manages almost everything?