Operations | Monitoring | ITSM | DevOps | Cloud

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.

Amazon Web Services is a comprehensive, well-supported cloud service that is continuously growing and evolving. As cloud technology continues to boom, enterprises all across the globe are increasingly depending on cloud service providers to manage their workloads, data, and applications.

Snapshots in Azure is a nice feature that allows you to take a read-only, “point in time” snapshot of a Virtual Machine’s disk. You can take a snapshot of a VM’s OS or data disk. You can use this snapshot to revert the VM to a point in time before an event occurred, or you installed something that didn’t go quite right.

One question we frequently hear from customers using the Microsoft stack is, “should I use Git or TFS?” The question requires a little decoding due to the way that Microsoft has shifted their brands over time. Here’s some background. Many people still refer to this as “TFS,” regardless of the version they are using. TFVC used to be the default type of repo for TFS projects.