Being innovative is like being handsome. It only counts when others think so. When Bank of America honors you for being innovative and improving how their 30,000 developers perform, it’s a very handsome compliment. At the 11th Bank of America Technology Innovation Summit, JFrog was recognized for industrial leadership and excellence in providing global business solutions. This year, JFrog was one of only two technology companies honored for its strong partnership with the firm.

During the past years we made plenty of contributions to improve the current state of the Windows monitoring. We tried to improve the actual installation with the Icinga 2 Powershell Module, allowing users to easier automate installation and configuration of Icinga 2. On a long term we however wanted to improve the monitoring of Windows infrastructures entirely, by not only providing new plugins but also to increase the contribution by the community.

If you’ve worked on a team that has adopted Agile techniques, you’ve probably heard of a retrospective. If not, here’s the TL;DR: A retrospective is a meeting in which a team connects regularly to reflect on what happens throughout a project and continuously improve how they work moving forward.

Amazon MQ is a managed ActiveMQ messaging service hosted on the AWS cloud. Amazon MQ’s brokers route messages between the nodes in a distributed application. Each broker is a managed AWS instance, so your messaging infrastructure doesn’t require the maintenance and upfront costs of a self-hosted solution.

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.

“With cybercrime heading into the tens of billions of records stolen, and trillions of dollars in damages, we are proud to recognize ManageEngine as an award-winning innovator that offers a new approach to defeat these criminals,” said Pierlugi Paganini, editor-in-chief, Cyber Defense Magazine.

You might have seen a few of my tutorial videos on Grafana and Grafana Loki. If not, check them out here. These videos are a bit of an experiment to showcase the awesome work being done by the Grafana OSS community and for me to understand the technology better. I got a lot of encouraging feedback on the videos, so I plan to continue making them. A few folks also wanted to know why and how I created them. Happy to share the details here with you, and I look forward to your Grafana videos :)

Managed Service Providers (MSPs) are on the hook to deliver reliable, performant, and secure services to their customers. Production issues or security incidents can threaten SLAs, customer contracts, and ultimately business reputations. To state the obvious, MSPs need to understand what is going on in their environment so they can effectively identify and diagnose production issues before they impact customers. This is the idea behind “observability.”