Operations | Monitoring | ITSM | DevOps | Cloud

As you analyze your logs for application performance, infrastructure errors, system events, and more, sometimes you may need to look back to logs you were previously analyzing to help correlate events and identify the root cause of a problem. To help, we are excited to introduce Google Cloud Logging recent queries, to make it easy to track and run your past searches as you deep dive on your log data.

Engineering teams that build, scale, and manage cloud-based applications on AWS know that at some point in time, their applications and infrastructure will be under attack. But as applications expand and new features are added, securing the full scope of an AWS environment becomes an increasingly complex task. To add visibility and auditability, AWS CloudTrail tracks the who, what, where, and when of activity that occurs in your AWS environment and records this activity in the form of audit logs.

Over the past several months we’ve been focused on improving observability and operations workflows for Compute Engine. Today, we are excited to share the first wave of these enhancements are now available. These include: Significantly improved operating system support for the Cloud Monitoring and Cloud Logging agents. The ability to rapidly deploy, update, and remove agents to groups of VMs, or all of your VMs, by policy, with as little as a single gcloud command.

Many organizations are adopting centralized logging tools so that they have one place for all of their data. This is generally easier than having separate tools across teams for log storage and analysis. But centralized logging introduces new challenges, like how to segment those logs according to the teams or developers where they are the most relevant. And, how to manage log volume.

I would like to share our recent case study on our battling a very serious performance issue whose solution turned out to be a small change in code, but with a huge impact on all of our HTTP endpoints in our platform.