Much like the pagers of yore, PagerDuty immediately notifies the right person when something goes wrong. That means that no matter when there’s an issue in your application, the right people on your team will hear about it. But as much as we love PagerDuty, we’re not using valuable company time and resources just to tell you about it. We are, however, using valuable company time and resources to tell you all about our new integration with PagerDuty.

Regardless of the strength of your product, and the quality of your code, if the end result isn’t happy customers… What’s the point? For Tackle, a software company dedicated to helping ISVs turn the Cloud Marketplaces into repeatable, sustainable, and significant sources of revenue, customer experience is everything. As a software company serving other software companies, Tackle knows exactly what matters most to its customers, which is why they use Sentry.

In typical San Francisco startup fashion, we have our own set of “these are the things we stand by” company values. While we don’t aspire to churning out motivational poster-style blurbs, we do want to accurately reflect what’s important to our mission and vision — the principles that drive these forward. And, ok… Yes, these will likely end up on a poster of sorts. Just not the motivational type. And with way better design work.

Your customers are messaging, ordering, watching on a mobile device and — without a pause — carrying that experience to the web, desktop, tv, smart speaker, etc. Their expectations are that your service provides one seamless experience that goes with them where ever they are. That’s why you need resolution tools that work across organizational and technical boundaries. Now, maybe you’re tired of using an additional mobile focused tool when Sentry can cover both cases.

Sentry, the market leader in application monitoring, announced 200% growth with enterprise customers, scaling to a total of 18,000 paid customers. The company’s cloud, open-source, and single-tenant offerings now support more than 50,000 teams and 1 million developers globally, including Microsoft, Atlassian, Disney, Nike, Cloudflare, Autodesk, PayPal, Reddit, Peloton and many more of the world’s most well-known brands.

At its core, Sentry is a tool that alerts you to defects in your production software. But it does more than blast stack traces into your inbox: Sentry provides powerful workflows to help your team determine root cause, triage issues to your team, and keep tabs on ongoing concerns with comments and notifications. These collaborative features can help you resolve problems with your software quickly.

Sentry makes it pretty easy to connect a customer-facing issue right to the line of code, the release, and even the commit that caused it. At least that’s what developers tell us on Twitter. But you’re rarely working with obvious errors or errors affecting just one user. That’s why we added some new features to Discover and made diagnosing root causes even easier.

Customer support teams are a crucial part of any enterprise service, and in the world of Governance, Risk, and Compliance (GRC) Software, these teams need to be focused on supporting critical customer needs, not troubleshooting application errors that have reached the customer. Sentry has proved to be a pivotal part of the toolset for industry-leading GRC software company Reciprocity.

Early last year, we launched the Integration Platform to enable any developer to easily create integrations and workflows on top of Sentry. As we continue to build out the platform, we want to give developers visibility into how their integrations are doing. With that, we present the Integration Dashboard!

Continuous integration tools like CircleCI let developers automate builds and tests, so that teams can merge changes into their codebase quickly and frequently. In this article, we’ll take a look at how to combine Sentry’s command line interface with CircleCI to automatically create Sentry releases. This will unlock some of our best features, like identifying suspect commits that likely introduced new errors, applying source maps to see the original source code within Sentry, and more.