Operations | Monitoring | ITSM | DevOps | Cloud

Helping software producers achieve compliance with regulatory requirements has been a huge part of our focus at JFrog. That’s why many in the most regulated industries such as banking, finance, manufacturing, and retail are our customers for DevOps. We’re excited to announce that JFrog DevOps Platform solutions – JFrog Artifactory and JFrog Xray – are now available with native deployment templates for customers using AWS GovCloud (US) and Azure Government clouds.

CloudZero is a platform that helps you understand cost — but that doesn't mean it's purely a finance tool. In fact, unlike most other cloud cost management and optimization solutions, it’s built for engineering. However, CloudZero still makes a lot of finance teams very happy. First of all, the work that engineering teams do while using CloudZero saves money, which every finance team appreciates.

We're excited to announce that autoscaling is now available on Elastic Cloud. In our initial release, autoscaling monitors the storage utilization of your Elasticsearch data nodes and the available memory capacity for your machine learning jobs.

One of the serverless best practices is one-purpose functions. You should keep your Lambda functions small and solve exactly one use-case. This way, you can optimize them better and keep potential security problems contained. But creating many small functions can get overwhelming quickly. Even small projects can end up with more than 20 Lambda functions.

With our ability to ingest GCP logs and metrics into Splunk and Splunk Infrastructure Monitoring, there’s never been a better time to start driving value out of your GCP data. We’ve already started to explore this with the great blog from Matt here: Getting to Know Google Cloud Audit Logs. Expanding on this, there’s now a pre-built set of dashboards available in a Splunkbase App: GCP Application Template for Splunk!

Microsoft Azure has just announced the details of its new Azure Arc Validation Program, aiming to further increase customer confidence in deploying Arc enabled Kubernetes in production workloads, and at scale.

In Part 1 of this series, we looked at the important metrics to monitor when you’re running ECS or EKS on AWS Fargate. In Part 2 we showed you how to use Amazon CloudWatch and other tools to collect those metrics plus logs from your application containers. Fargate’s serverless container platform helps users deploy and manage ECS and EKS applications, but the dynamic nature of containers makes them challenging to monitor.

AWS Fargate provides a way to use AWS container orchestration services—Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS)—without needing to provision and maintain the infrastructure that runs your containers. Fargate is similar to serverless container platforms from Google (Cloud Run) and Microsoft (AKS virtual nodes).

In Part 1 of this series, we showed you the key metrics you can monitor to understand the health of your Amazon ECS and Amazon EKS clusters running on AWS Fargate. In this post, we’ll show you how you can: You can use Amazon CloudWatch and related AWS services to gain visibility into your ECS clusters and the Fargate infrastructure that runs them.