Software does not expire, but it “rots”. Its quality degrades over time. As you build your project and add features, you probably won’t always build it in a clean, orderly and mindful way. Especially if you have a tight deadline. So aside from features, you also produce bugs, code smells, and technical debt. That “rots” your software, but your job as a software engineer is to maintain its “freshness” while building on top of it.
Last year we introduced Sentry Cron Monitoring (beta) to help developers get code-level context and performance trends for their scheduled jobs. While Crons remains in beta, we’ve heard your feedback over the past few months and want to share some big improvements we’ve shipped. In this post, we’ll cover how we’ve simplified the setup process by integrating Crons into our SDKs and automating monitor setup for select frameworks.
The month of May has just ended and pretty much everybody agrees that 2023 is absolutely flying by. Here at Sentry, we’re looking to match the speed of 2023 with our own velocity of new product releases. Here they are in a nutshell.
We’re happy to announce that the Sentry SvelteKit SDK is now generally available and ready to help you monitor your SvelteKit application. Last year, we entered the Svelte ecosystem by creating an SDK for Svelte, which provides support for Svelte single page apps. We knew that SvelteKit was already quite far along back then and we kept a close eye on its development. We also received a lot of requests from the community to support SvelteKit.
How frustrating is it when you’ve just landed on a web page, you click on a certain element and an ad or something else pops up and you end up clicking that thing instead? That’s a layout shift, which is bad for the user’s experience and the later they happen, the worse it is. Research from HTTP Archive shows that over 80% of websites use web fonts. Web fonts also cause layout shifts, if they’re not being loaded strategically.
In our daily lives as developers, we have to deal with a lot of code that we did not write ourselves (or wrote ourselves but already forgot that we did). We use tons of libraries that make our lives easier because they deal with complex stuff like machine learning, time zones, or printing. As a result, much of the code base we work with on a daily basis is a black box to us. But there are times when we need to learn what is happening in that black box.
Users are complaining about slow load times and you’ve thrown logs, traces, and metrics — heck, the entire kitchen sink of performance monitoring — at your application, but you still can’t figure out the source of the bottleneck. Maybe you missed adding instrumentation to something in the critical path, or you’re simply testing in an environment vastly different from the ones your users are experiencing in production.
As a developer, triage duty week was often the worst week of my month. Anytime a bug was reported, I’d search for the right environment, wander through logs, pray there was an associated stack trace, use my mental mapping of our code base, and route bugs to the right teams. Developers on triage rotation need to ensure bugs are routed to the correct team along with adequate information to help the team investigate the bug.
Building high quality, performant mobile apps is hard. Developers need to keep up with rapidly changing technologies, high user expectations, and competitive app stores. We sat down with Julius Skripkauskas and Walt Leung to discuss how mobile developers can build better mobile experiences, including choosing the right technology, focusing on the right KPIs, and staying on top of trends in device formats and AI.
You run an e-commerce website and notice a drop in sales on a specific product page. You suspect that users may be encountering an issue with the “Add to Cart” button, but you’re not sure what’s causing the problem. With Sentry Session Replay’s new search by user click feature, you can easily find replays where users clicked on that button and watch their sessions to see exactly what happened.
