If you’re a JavaScript developer there’s a very good chance you’ve heard of or use Vercel. In the small chance you haven’t, Vercel is this awesome platform that makes building and deploying Jamstack frameworks like Next.js incredibly fast and easy. Next.js is gaining in popularity with 51k stars on GitHub and it’s one of the most trusted stacks in the JavaScript world these days.
For as long as we can remember, Sentry has had some version of CSV Exports. They’ve been limited only 1000 rows of results, which did the job for the most part. However, the more you used Sentry, the more we found that limit wasn’t good enough. What if I told you there was a way to get all your data in the exports in a single CSV? That’s right, no more DIY python scripts. No more manually piecing CSVs together. No more feature-request tickets.
Time trolls people. It speeds up in good times and slows down in bad. For instance, when you push code, your brain feels like it’s in a whirlwind. But when you’re debugging subsequent errors, the hours seem to slog by. This is particularly true if you are operating without context and without the help of automation. Fortunately, our friends at GitHub built an automation platform for products like Sentry to integrate with: Sentry Release GitHub Action.
Lazy-loading is the most ironic term in programming. That’s because, instead of eating its third bowl of cereal on the couch, what lazy-loading actually does is make your User Interface more efficient. And efficient UI is important to us at Sentry. We don’t want our customers tapping their feet and pointing to their imaginary watch while waiting for their page to load.
As the adoption of GraphQL is rising steadily, teams often come across the natural question of how to deal with errors that pass service boundaries and propagate from API endpoints to clients and consumers.
iPod to iPhone. Breaking Bad to Better Call Saul. Super Mario to Mario Maker. Leaders don’t rest on their laurels. That’s what motivated us to create Performance, our new code monitoring offering: to build off our core functionality and toward the demands developers face, both today and in the future.
Crashes are something we know a thing or two about. We see a lot of reasons why apps crash, but we also see when a lot of popular mobile apps crash at once, that’s something we notice. Crashes across many mobile apps at the same time is not typically a result of an app-specific code update. I mean, there’s a non zero chance that hundreds of developers published broken apps… but these widespread issues are likely a result of two things.
Among developers, alerts have a bad rep. But outside the coding environment, alerts can signify positive developments. For example, a microwave just alerted me that my burrito is ready to eat. Sentry’s new Metric Alerts is the microwave to the frozen burrito that is your code.
Over the past week, we rolled out access to Advanced Data Scrubbing for all users. If you were one of our Early Adopters, you’ve known about this for a couple of months. As the name implies, it’s an addition to our existing server-side data scrubbing features, meant to provide greater control and more tools to help you choose which data to redact from events. One of Sentry’s main selling points as an error monitoring platform is the data it collects and aggregates.
App Nouveau is a Canadian professional services company that builds transportation management system software. As developers of highly-specialized software solutions, App Nouveau needs a robust error monitoring tool to deliver world-class code required by its commercial clients. App Nouveau recently began using Sentry to uplevel a few key areas in the code development lifecycle. Chief Technical Officer Paito Anderson and his team decided to switch to Sentry just a few months ago.
