When your applications raise errors, you need a way to make sense of them so you can set priorities, start troubleshooting, and gauge the success of your efforts. Errors can appear within the thousands of browser sessions and backend hosts running your software, making it difficult to find meaning within the noise. This is especially true of frontend errors, where seemingly endless permutations of browser version, location, and other environmental details can make it hard to spot trends.

From gaming and social media to e-commerce and travel, mobile is reshaping the way businesses operate and engage with their customers. In an increasingly competitive market, ensuring your mobile applications stay highly performant and resilient will be critical in differentiating yourself from the crowd as well as avoiding uninstalls and poor app reviews.

Governance, risk, and compliance (GRC) are major inhibitors for organizations moving to the cloud—and for good reason. Cloud environments are complex, and even a single misconfigured security group can result in a serious data breach. In fact, asset misconfigurations were the leading cause of cloud security breaches in 2019. This puts a lot of pressure on developer and operations teams to properly secure their services and maintain regulatory compliance.

When your application experiences an outage, the tools your team uses to manage its response can make all the difference in how quickly they resolve the problem and avoid it in the future. An effective incident management workflow depends on accessible, integrated tools as well as clear, direct channels of communication. And, even after the matter’s been resolved, documentation and analysis of an outage is vital to ensuring it never happens again.

Today, at Dash 2020, we unveiled new products and features on the Datadog platform that provide engineering teams with even deeper visibility into their distributed applications and infrastructure. With these additions, Datadog further streamlines every step of your release cycle, from shift-left testing in your CI/CD pipelines to profiling your code in production.

During my career, I’ve taken part in many on-call rotations and post-mortems. The longest on-call rotation I’ve ever had — no breaks, vacations, or holidays — lasted for a whopping 2.5 years at Lucid Software. I’m jaded. I strongly prefer stability to tinkering with shiny new toys. Very few software engineers start this way, but enough of them make the transition after having been bit enough times by a bad release.

For our second community meetup we focussed on using Civo for CI/CD through GitOps and Github actions for cloud native application development This installment featured talks from our CTO Andy, our Developer Advocate Kai, and guest talks from community members Sam Weston and Johannes Tegnér. The talks touched on a wide variety of topics within CI/CD, from automating builds to monitoring and observability. Here's what was on the agenda...