On the surface, food delivery service seems straightforward. However, creating a food delivery startup is more like building a transportation and logistics company than pizza delivery. Coordinating web and mobile applications for seamless ordering, tracking, and delivery, all within razor-thin service windows, takes an unprecedented level of complexity (when you get it right). And once you begin to scale service, the technical challenges become even greater.

At Sentry, we often get asked how error monitoring is different from APM or logging. To help answer this, I’ve broken down the different types of monitoring into four major categories.

With a service designed to help remote teams run more efficiently, Tability’s success relies on application reliability and deliverability to help its users keep complicated projects on schedule. This is why Tability has relied on Sentry error monitoring to identify issues in code and scale development work efficiently.

Different development teams exercise different production philosophies. These philosophies usually stem from greater company direction and culture but are guided by the experience of technical leadership. Aumni has built a unique technology solution to unlock data insights into investment auditing and due diligence for VCs. They need to remain nimble and develop great code (areas 1 and 2) but reduce the probability of user-facing errors and the time spent detecting and fixes new issues (area 3).

Big ideas need creative solutions. Creative solutions mean solving out of the box engineering problems. When you’re solving these new problems, strong error monitoring is imperative to the development cycle. You don’t want to spend all your time chasing down issues and struggling to track the source of errors.

While powerful, our first iteration of Discover had some user experience complexities that made it less user-friendly than other potential search mechanisms. We also heard from you that our Events feature was useful for identifying individual events, but finding common patterns within those events was extremely difficult — keyword, ”was”. I want to share some of the features and the top 5 use cases that you can do with the refreshed Discover.

Here at Sentry, we use Travis CI, a continuous integration tool for GitHub that lets us automate our tests and view the results right within each pull request. In this blog post, we’ll walk through a quick example of how to automatically create Sentry Releases with Travis CI when a commit is pushed to your project’s master branch. (Sentry Releases enable some of our best features, like identifying the commits that likely introduced new errors, and much more!)

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.