Sentry is full of engineers, so we know how painful it can be to deal with breaking changes caused by third party libraries. But we also know those third party libraries have to continually update and stay on top of their games, or they’ll become irrelevant. For that reason, we try to only introduce breaking changes when they’re really (really) required. Especially when those changes are made to an API surface.

Pavlos is a Site Reliability Engineer based in Munich, Germany. He likes building software and expanding his knowledge around the reliability of services and their infrastructure. He has created a few open-source SRE projects such as the awesome-sre, Wheel of Misfortune, Availability Calculator, and awesome-chaos-engineering to assist teams and individuals in getting on board with the SRE culture.

You’ve no doubt heard that IOpipe has been acquired by New Relic (congratulations to both). As part of the acquisition, New Relic has said it intends to retire the IOpipe platform in the next 30 days. If you’re currently relying on the IOpipe platform to monitor and debug your serverless application you have an important decision to make. One option is to try out New Relic’s serverless monitoring functionality.

When we announced the launch of our Retrospectives Guide, we wrote about the value of scaling the continuous improvement mindset to beyond Product Development at PagerDuty by establishing the RetroDuty community. In this installment of our blog post series on retrospectives, I highlight the differences between postmortems and retrospectives. You might have heard of postmortems and/or retrospectives before reading our guides.

The issue of network baseline arose quite some time ago. Everything started from the understanding that networks are not static entities, but are a set of elements that change over time. It was also understood that networks are not only made up of physical and tangible elements, such as a router or a switch, but we must also have more abstract elements, such as the traffic pattern over a WAN link, for example.

This is the third and last in a series of articles on Amazon CloudTrail. In the first part of the series, we introduced AWS CloudTrail and how it works and saw where and how it saves its data. We then learned how to query CloudTrail logs in the second part of the series where we used Amazon Athena to find meaningful information from large volumes of CloudTrail data.

Team Exoprise had another fantastic show in Orlando last week at Microsoft Ignite 2019. We showed off our latest Teams Audio/Video Conferencing Sensor and a significant upgrade to Exoprise Service Watch including new capabilities to analyze Single-Page Apps (SPAs) which are quite common to modern SaaS applications.

We are pleased to announce that CloudSploit has joined the Aqua Security family. Aqua is the leading platform provider for securing container-based, serverless, and cloud native applications. CloudSploit rounds out its offering by adding our open-core Cloud Security Posture Management (CSPM) SaaS.

We're very exited to bring all the error monitoring and debugging capabilities of Rollbar to Salesforce Apex applications. According to Salesforce, millions of developers and thousands of independent software vendors develop customized applications using Apex to extend the fuctionality of Salesforce. A few months ago, when some of our customers reached out and asked us for an error monitoring solution for their Salesforce Apex developers, our engineering team jumped on the task.

Software systems inevitably encounter situations that can cause failures and malfunctions which affect user experience, data integrity, and security. In this blog post, we will learn how to avoid these situations though Exception handling. We will focus on software exceptions and how to address them using Hypertext Preprocessor, or PHP.