Share on Twitter
Share on Facebook
Share on HackerNews
Share on LinkedIn

Introducing Insights: Tailored debugging workflows for your application

You’re seeing an unusually high number of 429 status codes, but your monitoring solution can’t tell you much beyond that. Typically, that’s when you start searching through logs — while simultaneously sustaining the urge to walk away and hope someone else deals with it.

To make sure neither of those happens, we made a new set of debugging workflows aptly named Insights. Available on our Business and Enterprise plans, Insights helps you easily gut-check key components of your application, the infrastructure, and the APIs it relies on, and drill down to the specific function or line of code causing that spike of 429s. And just like every great infomercial - but wait, there’s more!

Trace slow Web Vitals to their root cause

Sentry Insights helps you track all Core Web Vitals, and trace performance issues directly to the function or line of code causing the slowdown.

Imagine your store just dropped the latest sneaker. Sneakerheads from everywhere land on your page, but the main image takes a while to load, leaving many to bounce to another store that they already have loaded in another tab. This is a common LCP (Largest Contentful Paint) issue, where the largest piece of content—an image or text block—takes too long to appear on the screen, leading users to think the page is broken.

Sentry’s Web Vitals Insights helps you monitor LCP so you can see how long it takes for the largest content element to render. Sentry also shows you the pages with the most significant opportunity for improvement and lets you dive into them for further troubleshooting.

With tracing, you can then start from the poor LCP score and use the spans in the trace to quickly identify the associated element and resource that’s causing delays. Then, with Sentry’s Profiling, you can diagnose the root cause by identifying which code the browser was blocked on during the loading process.

Debug slow mobile screen loads

Whether it’s a missed package due to a slow-loading doorbell stream or being late to an important meeting because your conferencing app takes too long to start. Every second counts (yes, we watch The Bear too).

Screen Loads Insights provides an overview of your mobile app’s screen loading times, allowing you to compare performance across releases, monitor regressions, and assess user impact. It will even guide you to the specific code causing issues, so you can quickly halt rollouts or push fixes when necessary.

As a refresher, Screen Loads tracks two key metrics:

  1. TTID (Time to Initial Display): How long it takes for a user to see the first frame, indicating that the app is loading.
  2. TTFD (Time to Full Display): The time it takes for the app to become fully interactive with all content loaded.

With Screen Loads, you can view the most active screens in your app and filter by the most time-consuming operations, causing your TTID or TTFD to be slow. From there, you can jump into a specific operation, see connected issues, and additional debugging context like version, device, and network variables. So the next time your users complain it’s taking forever to log into your app, you can trace from the time-consuming span to the code changes, dependencies, or assets causing the slowdown.

Connect slow database queries to code

While monitoring Web Vitals and mobile UI behavior is important, it’s only half the story. Since most frontend performance issues are caused by the backend, we’ve added several backend Insights, including Queries.

Queries Insights provides a view into your database performance, allowing you to see your most time-consuming queries and how they impact your application’s performance.

So the next time a customer can’t add new shoes to their cart or their login times out, you can quickly see where there are spikes in duration and dive deeper to see the performance impact — including where in the code it’s triggering the issue.

Additionally, we’ll show you the exact query with syntax highlighting, and if your GitHub repository is linked to the project, you can navigate directly from Sentry to the specific line in your code.

Getting started with Insights

To start using Insights, you must have Tracing enabled and be on a Business or Enterprise plan. Check out the docs for a full list of Insights, or head to your Sentry account and click on ‘Insights’ in the nav to try it out now.

If you’re new to Sentry, you can try it for free today or request a demo to get started.

Last, you can always read more in our blog about our latest Insights like LLM monitoring, Outbound Requests, Caches, Queues, App Starts, and Screen Loads.


The best way to debug slow web pages

Hear from ‪@whitep4nth3r‬: Tools like Page Speed Insights and Google Lighthouse are great for providing advice for front end performance issues. But what these tools can’t do, is evaluate performance across your entire stack of distributed services and applications.

Watch Me

More from the Sentry blog

ChangelogCodecovDashboardsDiscoverDogfooding ChroniclesEcosystemError MonitoringEventsGuest PostsMobileOpen SourcePerformance MonitoringRelease HealthResourceSDK UpdatesSentry
© 2024 • Sentry is a registered Trademark
of Functional Software, Inc.