Operations | Monitoring | ITSM | DevOps | Cloud

In Part 2 of this series, we showed you how to use CloudWatch to monitor metrics and logs from Amazon MQ. With CloudWatch, you can easily create ad-hoc graphs to visualize the performance of your messaging infrastructure and other AWS services you use (such as EC2, Lambda, and S3). But to monitor your Amazon MQ brokers, destinations, and clients alongside the rest of your applications and infrastructure, you need a monitoring platform that easily integrates with your whole technology stack.

To centralize logging from your entire stack—from traditional infrastructure to serverless components—Datadog is announcing native support for the launch of FireLens for Amazon ECS. FireLens streamlines logging by enabling you to configure a log collection and forwarding tool such as Fluent Bit directly in your Fargate tasks. We’ve partnered with AWS to provide built-in Fluent Bit support for Datadog so that you can now seamlessly route container logs from AWS Fargate.

At JFrog, we think enabling DevSecOps in the cloud should be as easy as ordering from a drive-up window. Getting the tools you need for digital transformation should only be a short stop on your long journey. And you should be able to get it your way, on the cloud services platforms you choose. That’s why we’re excited to announce the availability of JFrog Cloud Pro X on Azure Marketplace.

It’s been almost two weeks since we said goodbye to Virtual Instruments, and hello to Virtana – a company focused on helping customers take a modern, AIOps-empowered approach to managing their hybrid IT infrastructure. As part of introducing the world to Virtana, we also announced the launch of the latest addition to our portfolio of hybrid infrastruture monitoring solutions – CloudWisdom.

I often get asked what software tools are ideal for a serverless developer. I like being asked for my tooling preferences as much as the next developer gal, but when you break it down, this particular question is flawed. Serverless is, after all, about using a massive suite of platform tools to let you do minimal management.

Prior to version 2.3, new versions of Kubernetes came out with point releases of Rancher and required an upgrade to Rancher before they were made available for use. Rancher 2.3 changes that pattern and now makes it possible to update the metadata store for available Kubernetes versions, disconnecting the Rancher server upgrade process from the Kubernetes cluster upgrade process.