We’re pleased to come home from DattoCon19 with memorable experiences. It was a well-curated conference, striking a fine balance between emerging MSP trends, informative sessions, networking and of course, entertainment. Here are my top takeaways from the event.
This week at re:Inforce in Boston, the AWS team showed off its Security Hub service—a powerful service that provides SecOps teams a comprehensive view of their high-priority security alerts and compliance status across their AWS accounts. We’re excited to join AWS at re:Inforce this week as a Security Hub partner, where we’ll show users how PagerDuty and AWS Security Hub work together to provide real-time SecOps to any team using AWS.
To keep you up-to-date with what’s going on in anomaly detection, we keep an ongoing list of the biggest glitches happening in the business world. Here is what made waves in June. June 25, 2019 When Dutch telco KPN suffered a major outage on the evening of Tuesday, June 25, the 112 emergency number was also knocked out across the country. “We have no reason to think it was (a hack) and we monitor our systems 24/7,” the company spokesperson told Reuters.
Companies invest in anomaly detection in order to proactively identify risks, such as revenue loss, customer churn and operational performance issues. Anomaly detection essentially enhances traditional BI and visualization tools, venturing beyond a summary view of your data. It constantly scans every metric, at a granular level, to find abnormalities. But in order for this technology to have an impact, you must be able to trust it.
On June 20 we have released the 3rd update for EnterpriseAlert 2019. Don’t get confused by the version number, 8.2.0 would better be 8.3.0, but that’s the way it is. Here is a very short EA 2019 release history for CY 2019.
Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we discuss whether NoOps is just a buzzword, a far-fetched reality, or simply the next evolutionary state of DevOps.
The PagerDuty Incident Response Process is a detailed document that provides a framework for how to structure your incident response process. But sometimes it helps to understand how these seemingly abstract concepts play out during real-world scenarios. You can now hear an incident call recording that’s based on a real PagerDuty incident. Due to the nature of incident response practices, the process guide we publish is filled with very explicit details regarding a variety of situations.
While there are some very good sources out there on how to manage a critical incident, Google also wrote a chapter on incident management in their book, “Site Reliability Engineering”. In this chapter, the folks at Google present their approach to a well-designed critical incident management process.
