Operations | Monitoring | ITSM | DevOps | Cloud

In part 2 of our AWS S3 Monitoring series, we covered the basics of AWS S3 logging, why it’s important to log all the information in your cloud environment, and also the benefits of monitoring those logs. Now, AWS offers some great tools for monitoring and log querying, but if you and your team want to take it to the next level, Sumo Logic is there for your needs.

As an engineer who has set up logging for more than one deployment or environment, you know that you usually have one logging account per deployment. You’ve got plenty of pre-created queries, graphs, and alerts set up specific for your company’s use case, all of which are vital to you knowing the health of your infrastructure. Now imagine being responsible for creating and maintaining logging accounts across 10+ deployments.

Logz.io was born out of a frustration with the realities of managing an open source monitoring and troubleshooting stack across distributed systems at cloud scale. Today, we introduce another tool to streamline log mamagement: Log Patterns.

It’s 3 AM and your phone is ringing. Rubbing your eyes, you take a look at the alert you just got from PagerDuty. A critical service has just gone offline. Angry customers are calling support. Your boss is on the phone, demanding the issue be resolved ASAP. You open up your log management tool only to be faced by 5 million log messages. What now?

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.