On any given day, we use rideshare apps to get from one place to another. We check public transportation apps to see when the next train is arriving at the station. We use streaming services to watch Frasier at the end of lo-ooo-ng work days. As part of engineering teams, we use application monitoring and cloud services (like CI and cloud infrastructure) to function, so that code changes seamlessly deploy into production.
Sentry helps developer teams build the most reliable software. Our help often manifests in two distinct forms: resolving issues in your product and ensuring that issue resolution fits seamlessly into existing workflows. We recently launched our Integration Platform, which allows developers to build publicly available tools on top of Sentry. For the launch, we built many new features, while also making it easier to use existing ones.
According to Stack Overflow’s Developer Survey 2019, Go is the third most wanted language to learn, as well as the third-best paid technology in the field. It is not a surprise, as it is one of the languages used for writing critical parts of a lot of large systems. The language design and syntax are simple, but developing in Go is far from easy.
You probably use many tools to get through the day. Do you ever wonder what tools get other people through their days? In our Tools This Engineer Uses series, we explore the routines, systems, and tools your peers rely on to solve problems and accomplish goals. Liz Krane, Sentry’s new Developer Advocate, is no stranger to meetups. She created and continues to run Learn Teach Code, the second-largest tech meetup in Southern California with over 9,500 members.
Welcome to our Sentry for Good blog post series, where we share the stories of organizations making a difference in the world while also positively influencing the broader developer ecosystem. In this post, we highlight Sentry customer and non-profit Code for America.
June and July are traditionally slow months. The sun is out, and there’s too much work reflecting off all our monitors for any of us to get much work done. For us, it’s doubly slow as we’re putting all of our efforts towards a big launch later this year. Still, some great stuff came out.
Welcome to our series of blog posts about things Sentry does that perhaps we shouldn’t do. Don’t get us wrong — we don’t regret our decisions. We’re sharing our notes in case you also choose the path less traveled. In this post, we’re giving context to everything that needed to happen before we introduced Snuba, our new storage and query service for event data.
Welcome to our series of blog posts about all the nitty-gritty details that go into building a great debug experience at scale. Today, we’re looking at the shortcomings of source maps. Other than Python, JavaScript is the oldest platform that Sentry properly supports, which makes sense considering many Python services (including Sentry itself) have a JavaScript front-end. As the popularity of transpiling grew, the need for tools to debug transpiled code in production became obvious.
In our Sentry for Data series, we explain precisely why Sentry is the perfect tool for your data team. The present post focuses on how we optimized Airflow for deeper insights into what goes wrong when our data pipelines break. Data enables Sentry’s go-to-market teams by generating high-quality leads and tailored marketing campaigns. Of course, data is also used to steer the business by influencing how we think about Sentry pricing, future opportunities, and feature roadmap.
Errors suck. And you don’t want to spend too much of your time fixing them, dealing with them, investigating them, etc. In our Workflow blog post series, we look at how to optimize your, well, workflow, from crash to resolution. At this point in our workflow (check out the first and second posts in this series), we’ve minimized the impact of errors on the development process by creating infrastructure and culture equipped to handle unexpected issues.
