--- title: Firebase Performance Monitoring launches deeper... description: Firebase Performance Monitoring adds a new session drill-down feature that lets developers inspect individual trace instances rather than only aggregated data.... canonical: https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Firebase Performance Monitoring launches deeper performance insights | daily.dev og:description: Firebase Performance Monitoring adds a new session drill-down feature that lets developers inspect individual trace instances rather than only aggregated data.... og:url: https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s og:image: https://api.daily.dev/og/posts/ZJIDskx4S.png og:image:alt: Firebase Performance Monitoring launches deeper performance insights og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Firebase Performance Monitoring launches deeper performance insights **[Firebase](https://daily.dev/sources/firebase-blog)** · 4 min read · 0 upvotes · 0 comments ## Summary Firebase Performance Monitoring adds a new session drill-down feature that lets developers inspect individual trace instances rather than only aggregated data. The feature surfaces device properties, concurrent traces and network requests, and CPU/memory usage around a specific performance issue. A worked example shows how a slow product image load trace correlates with a large network request and a CPU/memory spike, helping developers pinpoint root causes faster. Available for iOS and Android via the Firebase docs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What new feature did Firebase Performance Monitoring add for investigating slow traces? Firebase Performance Monitoring added the ability to drill into individual sessions of a trace, showing device properties like app version and OS version, other traces and network requests happening at the same time, and CPU and memory usage. This lets developers see the context around a specific slow trace instance instead of only aggregated data across all samples, making it easier to pinpoint root causes such as large network requests or memory spikes. _Developers debugging mobile app performance issues can find release rundowns like this on daily.dev._ ### How can I find the root cause of a slow trace in Firebase Performance Monitoring instead of just seeing aggregated averages? Use the new sessions view, accessible from the top bar of the metrics detail page, to narrow down sessions by percentile range of trace duration and inspect individual trace instances. In one example, a productImageLoading trace running at the 90-95th percentile took 2.85s, coinciding with a 2MB network request and matching spikes in CPU and memory usage, revealing the image size as the bottleneck. _Track tooling updates like this session drill-down feature on daily.dev when hunting down app bottlenecks._ ## Similar posts on daily.dev - [Datadog delivers millions of in-depth performance insights with ProfilingManager](https://daily.dev/posts/datadog-delivers-millions-of-in-depth-performance-insights-with-profilingmanager-gnkgkmtm5) · Android Developers Blog · 0 upvotes · 0 comments - [A faster way to pinpoint performance bottlenecks: Using Profiles Drilldown with Grafana Cloud Knowledge Graph](https://daily.dev/posts/a-faster-way-to-pinpoint-performance-bottlenecks-using-profiles-drilldown-with-grafana-cloud-knowle-wlna1atud) · Grafana Labs · 5 upvotes · 0 comments - [Deep troubleshooting and crash intelligence in the new Dynatrace RUM experience](https://daily.dev/posts/deep-troubleshooting-and-crash-intelligence-in-the-new-dynatrace-rum-experience-0js0khmph) · Dynatrace · 0 upvotes · 0 comments - [Optimize your Firebase Remote Config usage](https://daily.dev/posts/optimize-your-firebase-remote-config-usage-woddfd7ym) · Firebase · 1 upvotes · 1 comments - [Troubleshoot frontend performance with Datadog’s Browser Profiler](https://daily.dev/posts/troubleshoot-frontend-performance-with-datadog-s-browser-profiler-m5lku2eug) · Datadog · 1 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Firebase Performance Monitoring launches deeper performance insights","url":"https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s"},"datePublished":"2026-08-23T12:17:50.118Z","dateModified":"2026-08-23T12:25:47.598Z","description":"Firebase Performance Monitoring adds a new session drill-down feature that lets developers inspect individual trace instances rather than only aggregated data....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,firebase","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Firebase Performance Monitoring launches deeper performance insights"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/firebase-performance-monitoring-launches-deeper-performance-insights-zjidskx4s#faq","mainEntity":[{"@type":"Question","name":"What new feature did Firebase Performance Monitoring add for investigating slow traces?","acceptedAnswer":{"@type":"Answer","text":"Firebase Performance Monitoring added the ability to drill into individual sessions of a trace, showing device properties like app version and OS version, other traces and network requests happening at the same time, and CPU and memory usage. This lets developers see the context around a specific slow trace instance instead of only aggregated data across all samples, making it easier to pinpoint root causes such as large network requests or memory spikes. Developers debugging mobile app performance issues can find release rundowns like this on daily.dev."}},{"@type":"Question","name":"How can I find the root cause of a slow trace in Firebase Performance Monitoring instead of just seeing aggregated averages?","acceptedAnswer":{"@type":"Answer","text":"Use the new sessions view, accessible from the top bar of the metrics detail page, to narrow down sessions by percentile range of trace duration and inspect individual trace instances. In one example, a productImageLoading trace running at the 90-95th percentile took 2.85s, coinciding with a 2MB network request and matching spikes in CPU and memory usage, revealing the image size as the bottleneck. Track tooling updates like this session drill-down feature on daily.dev when hunting down app bottlenecks."}}]} ```