Operations | Monitoring | ITSM | DevOps | Cloud

As our lives increasingly move online and data becomes the lifeblood of business, secure data transmission is imperative. From personal conversations to financial transactions, from healthcare records to sensitive business data, nearly everything we do online requires trust that our data is protected. And if you've ever made an HTTPS request, TLS is behind it, providing that trust.

Talking to many of our customers with different needs and use cases, one particular issue comes up all the time. When I'm seeing so many error groups in my app and so many error notifications in my inbox every day, it's easy to end up feeling overwhelmed. I want a more proactive system to alert me to which errors need attention and when, so that I can stop getting buried. Does this hit home? Then this article is written for you, the tech leads and the product managers who are on the front-line of issue prioritization.

We all know the pain and frustration associated with broken software. It's no secret that the internet is rife with broken links, slow pages, and broken shopping carts, often feeling like it's being held together with glue and duct tape. These issues aren't just causing frustration for customers; it costs businesses millions. According to the Consortium for Information and Software Quality, poor software quality cost US companies $2.08 trillion in 2020. Every interaction between a customer and your technology is an opportunity to build or destroy trust.

The Software Development Life Cycle (SDLC) describes the process we follow to deliver software to customers. It captures each step of creating software, from ideation to delivery and eventually to maintenance. In this post, we've broken down everything you need to understand the SDLC.

After introducing Raygun's original MCP server and our new remote-first version, the most common question we hear is: "How do I actually set this up and start using it?" This guide covers exactly that, two short videos walking through setup and a real error being solved in both Cursor and Codex.

Like any leadership role, leading an engineering team in a mature, compact company like Raygun comes with both honor and responsibility. Leading a major development project is a bit like conducting a symphony orchestra, where every individual plays a crucial role and has a great impact on the work they release to customers and end-users.

If you're reading this blog, you likely already know the importance of quality software. But with the overwhelming number of metrics that can be monitored and improved, development teams are struggling with what metrics they should prioritize to have the most significant impact. The Crash Free Users score in Raygun is a perfect place for development teams who care about software quality to focus their efforts. It tells you what percentage of users didn't encounter a crash or error while using your software and is an ideal north star to gauge the overall quality of your software.

For the team that's down in the trenches untangling legacy code, writing unit tests, and just trying to come up with sensible variable names, it's easy to lose sight of the other end of the process, where code meets customer. You test, you deploy, nothing breaks, and you move on. However, it's just as important to keep an eye on code quality in production, and how it's experienced. Experience, though, is hard to quantify. What do you measure? How do you measure it? How do you improve it? And why do you care? We lay out answers in this post.

Here at Raygun, we like to go fast. Really fast. That's what we do! When we see something that isn't zooming, we try to figure out how to make it go faster. So today, we're answering a simple (and relevant) question; how do we make our public site, raygun.com, much, much faster? The answer, at first glance, is simple-we build it into a Content Delivery Network (CDN). But what if you have a load balancer serving your website, and you don't want to rebuild everything to serve from a CDN? Well, that's more complicated. Let's start by describing the issue.