Operations | Monitoring | ITSM | DevOps | Cloud

First time this year, multi-cloud enterprises, as a customer segment of Sumo Logic, have grown faster than any other segment: 50% Y/Y. What took so long? In my conversations with enterprises over the last 5 years, there was only one strategy for public cloud and it was multi-cloud. But evidence of multi-cloud usage was sparse at best. Data from our Continuous Intelligence Report in previous years didn’t find much to support that the strategy for multi-cloud was being implemented.

In Part 1 of this series, we saw how Amazon MQ routes messages between services in a distributed application, and we looked at some of the key metrics that describe the performance of the message broker and its destinations. Now that we’ve introduced the metrics and their meaning, we’ll look at some tools you can use to collect and query metrics from Amazon MQ:

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.

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.

Lights, Cameras, CHAOSSEARCH Yesterday, Thomas and I had the opportunity to sit down with AM and Nicki from the AWS Twitch series, Build with AM & Nicki. If you’re unfamiliar with the series, it’s definitely a must watch for all things AWS, with a high focus on the different services you can leverage to build products or applications for your business.

This article describes how SIGNL4 can be generally authorized as an enterprise app for Azure AD users (Marketplace Link). This is important if you want to implement the use of SIGNL4 in your company with existing user accounts from the Azure AD.

In this article we’ll introduce the AWS Cloud Development Kit and explore how it can boost the productivity of your development and infrastructure teams. Infrastructure-as-Code is fast emerging as a de-facto standard for development organizations.

In a recent post, we talked about AWS CloudTrail and saw how CloudTrail can capture histories of every API call made to any resource or service in an AWS account. These event logs can be invaluable for auditing, compliance, and governance. We also saw where CloudTrail logs are saved and how they are structured. Enabling a CloudTrail in your AWS account is only half the task.