На этой странице представлены советы по устранению неполадок, которые помогут вам начать работу с Performance Monitoring Performance Monitoring использовать его функции и инструменты.
Первые проверки для устранения неполадок
Следующие две проверки представляют собой общие рекомендации, которые следует соблюдать перед дальнейшим устранением неполадок.
1. Проверьте журналы на наличие событий, связанных с производительностью.
Проверьте сообщения в журналах, чтобы убедиться, что SDK Performance Monitoring фиксирует события, связанные с производительностью.
Откройте инструменты разработчика вашего браузера (например, вкладку «Сеть» в инструментах разработчика Chrome или «Монитор сети» в Firefox ).
Обновите веб-приложение в браузере.
Проверьте журналы на наличие сообщений об ошибках.
Через несколько секунд найдите в инструментах разработчика вашего браузера сетевой вызов
firebaselogging.googleapis.com. Наличие этого сетевого вызова показывает, что браузер отправляет данные о производительности в Firebase.
Если ваше приложение не регистрирует события, связанные с производительностью, ознакомьтесь с советами по устранению неполадок .
2. Проверьте панель состояния Firebase.
Проверьте панель состояния Firebase на случай, если обнаружен известный сбой в работе Firebase или системы Performance Monitoring .
Начало работы с Performance Monitoring
Если вы только начинаете использовать Performance Monitoring ( iOS+ | Android | Web ), следующие советы по устранению неполадок помогут решить проблемы, связанные с обнаружением SDK Firebase или отображением первых данных о производительности в консоли Firebase .
Firebase может определить, успешно ли вы добавили SDK Performance Monitoring в ваше приложение, когда получает информацию о событиях (например, о взаимодействиях с приложением). Обычно в течение 10 минут после запуска приложения на панели мониторинга производительности в консоли Firebase отображается сообщение «SDK обнаружен». Затем, в течение 30 минут, на панели мониторинга отображаются исходные обработанные данные.
Если с момента добавления последней версии SDK в ваше приложение прошло более 10 минут, а изменений по-прежнему нет, проверьте сообщения в журналах , чтобы убедиться, что Performance Monitoring регистрирует события. Для устранения проблемы с задержкой обнаружения SDK попробуйте выполнить соответствующие действия по устранению неполадок, описанные ниже.
Если вы всё ещё занимаетесь локальной разработкой, попробуйте генерировать больше событий для сбора данных:
Размещайте и просматривайте ваше веб-приложение в локальной среде.
Генерируйте события, загружая подстраницы вашего сайта, взаимодействуя с вашим приложением и/или запуская сетевые запросы. Убедитесь, что вкладка браузера открыта не менее 10 секунд после загрузки страницы.
Убедитесь, что объект конфигурации Firebase корректно добавлен в ваше приложение и что вы его не изменяли. В частности, проверьте следующее:
- Идентификатор веб-приложения Firebase (
appId) в объекте конфигурации указан верно для вашего приложения. Найдите свой идентификатор приложения Firebase в карточке «Ваши приложения» в проекта .
Если вам кажется, что с объектом конфигурации в вашем приложении что-то не так, попробуйте следующее:
Удалите объект конфигурации, который в данный момент присутствует в вашем приложении.
Следуйте этим инструкциям , чтобы получить новый объект конфигурации и добавить его в ваше веб-приложение.
- Идентификатор веб-приложения Firebase (
Если SDK регистрирует события, и всё, кажется, настроено правильно, но вы всё ещё не видите сообщение об обнаружении SDK или обработанные данные (через 2 часа), обратитесь в службу поддержки Firebase .
Убедитесь, что SDK Performance Monitoring корректно инициализирован в вашем приложении.
Убедитесь, что SDK Performance Monitoring не отключен с помощью следующего флага:
-
performance.instrumentationEnabled
-
Убедитесь, что кэширование в вашем браузере отключено , иначе браузер может не распознать новые настройки мониторинга.
Закройте, а затем снова откройте вкладку веб-страницы. Снова проверьте наличие записей в журнале.
Если вы только что добавили SDK Performance Monitoring в свое приложение, вам может потребоваться полностью перезапустить приложение, чтобы SDK начал работать.
Если вы не можете найти отключенные функции в своем приложении, обратитесь в службу поддержки Firebase .
Система Performance Monitoring обрабатывает данные о событиях, влияющих на производительность, прежде чем отобразить их на панели мониторинга производительности .
Если с момента появления сообщения «SDK обнаружен» прошло более 24 часов , а данные по-прежнему не отображаются, проверьте панель состояния Firebase на случай, если обнаружена известная проблема. Если проблемы нет, обратитесь в службу поддержки Firebase .
Общее устранение неполадок
Если вы успешно добавили SDK и используете Performance Monitoring в своем приложении, следующие советы по устранению неполадок помогут решить общие проблемы, связанные с функциями и инструментами Performance Monitoring .
Если вы не видите сообщений в журнале о событиях производительности , попробуйте выполнить следующие действия по устранению неполадок:
Убедитесь, что SDK Performance Monitoring корректно инициализирован в вашем приложении.
Убедитесь, что SDK Performance Monitoring не отключен с помощью следующего флага:
-
performance.instrumentationEnabled
-
Убедитесь, что кэширование в вашем браузере отключено , иначе браузер может не распознать новые настройки мониторинга.
Закройте, а затем снова откройте вкладку веб-страницы. Снова проверьте наличие записей в журнале.
Если вы только что добавили SDK Performance Monitoring в свое приложение, вам может потребоваться полностью перезапустить приложение, чтобы SDK начал работать.
Если вы не можете найти отключенные функции в своем приложении, обратитесь в службу поддержки Firebase .
В современных приложениях _fid отсутствует, поскольку параметр Interaction to Next Paint (INP) заменил First Input Delay (FID).
Для записи FID в старых браузерах:
Добавьте устаревший полифилл FID .
Убедитесь, что пользователь взаимодействует со страницей в течение 5 секунд после загрузки. Performance Monitoring регистрирует FID только в течение этого временного промежутка.
Вы видите данные о производительности для автоматически собранных трассировок , но не для трассировок пользовательского кода ? Попробуйте выполнить следующие действия по устранению неполадок:
Проверьте настройку трассировки пользовательского кода, инструментируемой через API трассировки , особенно следующие моменты:
- Названия для пользовательских трассировок кода и пользовательских метрик должны соответствовать следующим требованиям: отсутствие пробелов в начале и конце, отсутствие символа подчеркивания (
_) в начале, а максимальная длина — 32 символа. - Все трассировки должны быть запущены и остановлены. Любая трассировка, которая не запущена, не остановлена или остановлена до запуска, не будет регистрироваться в журнале.
Обратите внимание, что если вы используете метод
record(), то вам не нужно явно запускать или останавливать трассировку.- Названия для пользовательских трассировок кода и пользовательских метрик должны соответствовать следующим требованиям: отсутствие пробелов в начале и конце, отсутствие символа подчеркивания (
Убедитесь, что сбор данных Performance Monitoring не отключен с помощью следующего флага:
performance.dataCollectionEnabledЭтот флаг управляет сбором данных только для трассировки пользовательского кода (не для всех данных).
Проверьте сообщения в журналах , чтобы убедиться, что Performance Monitoring регистрирует ожидаемые трассировки пользовательского кода.
Если Performance Monitoring регистрирует события, но данные не отображаются в течение 24 часов, обратитесь в службу поддержки Firebase .
Если у вас отсутствуют данные о сетевых запросах, обратите внимание на следующее:
Performance Monitoring автоматически собирает метрики для сетевых запросов, поступающих через API браузера. Эти отчеты не включают неудачные сетевые запросы.
В зависимости от поведения вашего кода и используемых им сетевых библиотек, Performance Monitoring может сообщать только о завершенных сетевых запросах. Это означает, что открытые HTTP/S-соединения могут не отображаться в отчете.
Узнайте больше о том, как Performance Monitoring агрегирует данные сетевых запросов по шаблонам URL.
Вы также можете попробовать использовать пользовательские шаблоны URL-адресов !
Часто задаваемые вопросы
В продолжение недавнего внедрения системы оповещений, которая автоматически уведомляет вас о превышении установленных вами пороговых значений, мы заменили раздел «Наиболее актуальные проблемы» на «Недавние оповещения» . Раздел «Проблемы» теперь устарел и заменен на оповещения.
Селектор приложений в верхней части карточки «Производительность» фильтрует записи оповещений в разделе «Последние оповещения» . Отображаются только три самых последних оповещения для выбранного(ых) приложения(й).
Чтобы узнать больше об оповещениях, см. раздел «Настройка оповещений о проблемах с производительностью» .
Performance Monitoring поддерживает оповещения о метриках, превышающих заданные пороговые значения. Во избежание путаницы с этими настраиваемыми пороговыми значениями для метрик производительности мы убрали возможность настройки пороговых значений для проблем .
Мы заменили страницы «Подробности» и «Метрики» новым, централизованным пользовательским интерфейсом (UI), чтобы улучшить процесс устранения неполадок. Этот новый интерфейс для устранения неполадок предлагает те же основные функции, что и страницы «Подробности» и «Метрики». Чтобы узнать больше об устранении неполадок, см. раздел «Просмотр дополнительных данных для конкретной трассировки» .
Performance Monitoring собирает данные о производительности с устройств пользователей вашего приложения. Если у вашего приложения много пользователей или если оно генерирует большой объем данных о производительности, Performance Monitoring может ограничить сбор данных подмножеством устройств, чтобы уменьшить количество обрабатываемых событий. Эти ограничения достаточно высоки, чтобы даже при меньшем количестве событий значения метрик все еще отражали опыт использования приложения пользователями.
Для управления объемом собираемых данных Performance Monitoring использует следующие параметры выборки:
Ограничение скорости передачи данных на устройстве : Чтобы предотвратить внезапные всплески отправки трассировок устройством, мы ограничиваем количество трассировок кода и сетевых запросов, отправляемых устройством, до 300 событий каждые 10 минут. Такой подход защищает устройство от зацикливания измерений, которое может отправлять большие объемы данных о производительности, и предотвращает искажение результатов измерений производительности одним устройством.
Динамическая выборка : Performance Monitoring ежедневно собирает ограниченное количество трассировок кода и сетевых запросов для каждого приложения у всех пользователей приложения. На устройствах (с помощью Firebase Remote Config ) задается динамическая частота выборки, определяющая, следует ли случайному устройству собирать и отправлять трассировки. Устройство, не выбранное для выборки, не отправляет никаких событий. Динамическая частота выборки зависит от приложения и корректируется таким образом, чтобы общий объем собираемых данных оставался ниже установленного предела.
Пользовательские сессии отправляют дополнительные, подробные данные с устройства пользователя, что требует больше ресурсов для сбора и отправки этих данных. Чтобы минимизировать влияние пользовательских сессий, Performance Monitoring может также ограничить их количество.
Ограничение скорости на стороне сервера : Чтобы гарантировать, что приложения не превысят лимит выборки, Performance Monitoring может использовать выборку на стороне сервера для отбрасывания некоторых событий, полученных от устройств. Хотя этот тип ограничения не меняет эффективность наших метрик, он может вызвать незначительные изменения в закономерностях, в том числе следующие:
- Количество трассировок может отличаться от количества выполнений фрагмента кода.
- Трассировки, тесно связанные в коде, могут иметь разное количество выборок.
Вкладку «Проблемы» заменили функцией «Оповещения», которая автоматически уведомляет вас о превышении установленных вами пороговых значений. Вам больше не нужно вручную проверять консоль Firebase , чтобы узнать статус порогового значения. Подробнее об оповещениях см. в разделе «Настройка оповещений о проблемах с производительностью» .
Мы переработали раздел Performance Monitoring в консоли Firebase , так что на вкладке «Панель мониторинга» отображаются ключевые метрики и все трассировки в одном месте. В рамках переработки мы удалили страницы «На устройстве» и «В сети» .
В таблице трассировок внизу вкладки «Панель управления» содержится вся та же информация, что и на вкладках «На устройстве» и «Сеть» , но с некоторыми дополнительными функциями, включая возможность сортировки трассировок по процентному изменению для определенного показателя. Чтобы просмотреть все показатели и данные для конкретной трассировки, щелкните имя трассировки в таблице трассировок.
Просмотрите результаты трассировки на следующих вкладках таблицы трассировки:
- Трассировка сетевых запросов (как стандартная, так и пользовательская) — подвкладка «Сетевые запросы»
- Пользовательские трассировки кода — подвкладка «Пользовательские трассировки»
- Трассировка запуска приложения, приложения на переднем плане, приложения в фоновом режиме — подвкладка «Пользовательские трассировки»
- Трассировка отрисовки экрана — Подвкладка «Отрисовка экрана»
- Трассировка загрузки страницы — Подвкладка «Загрузка страницы»
Подробную информацию о таблице трассировки, а также о метриках и данных просмотра можно найти на странице обзора консоли ( iOS+ | Android | Web ).
Медленная отрисовка кадров и зависание кадров рассчитываются исходя из предполагаемой частоты обновления устройства 60 Гц. Если частота обновления устройства ниже 60 Гц, время отрисовки каждого кадра будет меньше, поскольку в секунду отрисовывается меньше кадров. Более медленное время отрисовки может привести к увеличению количества сообщений о медленных или зависших кадрах, поскольку больше кадров будут отрисовываться медленнее или зависать. Однако, если частота обновления устройства выше 60 Гц, время отрисовки каждого кадра будет меньше. Это может привести к уменьшению количества сообщений о медленных или зависших кадрах. Это текущее ограничение в SDK Performance Monitoring .
Если Performance Monitoring — единственный продукт Firebase в вашем приложении, вы можете использовать автономный SDK Performance Monitoring (и рекомендуемый ниже заголовочный скрипт), если вас это интересует:
- использование библиотеки с пространством имен
- уменьшение размера пакета SDK
- отложить инициализацию SDK до момента загрузки страницы.
To include the standalone Performance Monitoring SDK in your app and delay its initialization to after your page loads:
- Add the following script to the header of your index file.
- Make sure to add your app's Firebase project configuration object .
(function(sa,fbc){function load(f,c){var a=document.createElement('script'); a.async=1;a.src=f;var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(a,s);}load(sa); window.addEventListener('load',function(){firebase.initializeApp(fbc).performance()}); })(performance_standalone, firebaseConfig);
где,
- performance_standalone is
'https://www.gstatic.com/firebasejs/12.19.0/firebase-performance.js' - firebaseConfig is your app's Firebase config object
The above script asynchronously loads the standalone SDK then initializes Firebase after the window's onload event fires. This tactic reduces the impact that the SDK could have on page load metrics since the browser has already reported its loading metrics when you initialize the SDK.
You can create up to 400 total custom URL patterns per app and up to 100 custom URL patterns per domain for that app.
Near real-time data processing and display
Firebase Performance Monitoring processes collected performance data as it comes in, which results in near real-time data display in the Firebase console. Processed data displays in the console within a few minutes of its collection, hence the term "near real-time".
To take advantage of near real-time data processing, make sure your app uses a real-time compatible SDK version .
To take advantage of near real-time data processing, you only need to make sure that your app uses a Performance Monitoring SDK version that's compatible with real-time data processing.
These are the real-time compatible SDK versions:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
These are the SDK versions compatible with real-time data processing:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
If your app doesn't use a real-time compatible SDK version, you will still see all your app's performance data in the Firebase console. However, the display of performance data will be delayed by roughly 36 hours from the time of its collection.
Yes! Regardless of which SDK version an app instance uses, you'll see performance data from all your users.
However, if you're looking at recent data (less than roughly 36 hours old), then the displayed data is from users of app instances using a real-time compatible SDK version. The non-recent data, though, includes performance data from all versions of your app.
To view real time performance data, make sure that your app uses a Performance Monitoring SDK version that's compatible with real time data processing.
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
Contacting Firebase Support
If you reach out to Firebase Support , always include your Firebase App ID. Find your Firebase App ID in the Your apps card of your Project settings .
,This page provides troubleshooting tips for getting started with Performance Monitoring or using Performance Monitoring features and tooling.
First checks for troubleshooting
The following two checks are general best practices recommended for anyone before further troubleshooting.
1. Check log messages for performance events
Check your log messages to be sure that the Performance Monitoring SDK is capturing performance events.
Open your browser's developer tools (for example, Network tab for Chrome Dev Tools or in the Network Monitor for Firefox ).
Refresh your web app in the browser.
Check your log messages for any error messages.
After a few seconds, look for a network call to
firebaselogging.googleapis.comin your browser's developer tools. The presence of that network call shows that the browser is sending performance data to Firebase.
If your app isn't logging performance events, review the troubleshooting tips .
2. Check the Firebase Status Dashboard
Check the Firebase Status Dashboard in case there is a known outage for Firebase or for Performance Monitoring .
Getting started with Performance Monitoring
If you're getting started with Performance Monitoring ( iOS+ | Android | Web ), the following troubleshooting tips can help with issues that involve Firebase detecting the SDK or displaying your first performance data in the Firebase console.
Firebase can detect if you've successfully added the Performance Monitoring SDK to your app when it receives event information (like app interactions) from your app. Usually within 10 minutes of starting your app, the Performance dashboard of the Firebase console displays an "SDK detected" message. Then, within 30 minutes, the dashboard displays the initial processed data.
If it's been more than 10 minutes since you added the latest version of SDK to your app, and you're still not seeing any change, check your log messages to make sure that Performance Monitoring is logging events. Try the appropriate troubleshooting steps as described below to troubleshoot a delayed SDK detection message.
If you're still developing locally, try generating more events for data collection:
Serve and view your web app in a local environment.
Generate events by loading subpages for your site, interacting with your app, and/or triggering network requests. Make sure to keep the browser tab open for at least 10 seconds after the page loads.
Make sure that your Firebase configuration object is correctly added to your app and that you haven't modified the object. Specifically, check the following:
- The Firebase Web App ID (
appId) in the config object is correct for your app. Find your Firebase App ID in the Your apps card of your Project settings .
If anything seems wrong with the config object in your app, try the following:
Delete the config object that you currently have in your app.
Follow these instructions to obtain a new config object and add it to your web app.
- The Firebase Web App ID (
If the SDK is logging events and everything seems to be set up correctly, but you're still not seeing the SDK detection message or processed data (after 2 hours), contact Firebase Support .
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Performance Monitoring processes performance event data before displaying it in the Performance dashboard .
If it's been more than 24 hours since the "SDK detected" message appeared , and you're still not seeing data, then check the Firebase Status Dashboard in case there is a known outage. If there is no outage, contact Firebase Support .
Общее устранение неполадок
If you've successfully added the SDK and are using Performance Monitoring in your app, the following troubleshooting tips can help with general issues that involve Performance Monitoring features and tooling.
If you're not seeing log messages for performance events , try the following troubleshooting steps:
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Modern apps omit _fid because Interaction to Next Paint (INP) has replaced First Input Delay (FID).
To record FID in older browsers:
Add the legacy FID polyfill .
Confirm that the user interacts with the page within 5 seconds of load. Performance Monitoring records FID only during this window.
Are you seeing performance data for automatically collected traces but not for custom code traces ? Try the following troubleshooting steps:
Check the setup of custom code traces instrumented via the Trace API , especially the following:
- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
_) character, and max length is 32 characters. - All traces must be started and stopped. Any trace that is not started, not stopped, or stopped before started will not be logged.
Note that if you're using the
record()method, then you don't need to explicitly start or stop your trace.- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
Make sure that Performance Monitoring data collection is not disabled through the following flag:
performance.dataCollectionEnabledThis flag controls the collection of data for custom code traces only (not all data).
Check your log messages to make sure that Performance Monitoring is logging expected custom code traces.
If Performance Monitoring is logging events, but no data displays after 24 hours, contact Firebase Support .
If you're missing network request data, be aware of the following:
Performance Monitoring automatically collects metrics for network requests reported by the browser API. These reports do not include failed network requests.
Depending on the behavior of your code and networking libraries used by your code, Performance Monitoring might only report on network requests that are completed. This means that HTTP/S connections that are left open might not be reported.
Learn more about how Performance Monitoring aggregates network request data under URL patterns.
You can also try out custom URL patterns !
Часто задаваемые вопросы
We replaced Top Issues with Recent Alerts as a follow-up to our recent introduction of alerts, which automatically notify you when the thresholds you set are crossed. Issues are now deprecated and replaced by alerts.
The apps selector at the top of the Performance card filters the alert entries under Recent Alerts . Only the three most recent alerts for the app(s) selected are displayed.
To learn more about alerts, see Set up alerts for performance issues .
Performance Monitoring supports alerts for metrics that exceed defined thresholds. To avoid confusion with these configurable thresholds for performance metrics, we removed the ability to configure thresholds for issues .
We replaced the Details and Metrics pages with a newly redesigned, centralized user interface (UI) to improve how you troubleshoot issues. This new troubleshooting UI offers the same core functionality that Details and Metrics offered. To learn more about troubleshooting, see View more data for a specific trace .
Performance Monitoring collects performance data from your app's user devices. If your application has many users or if the app generates a large amount of performance activity, Performance Monitoring might limit data collection to a subset of devices to reduce the number of processed events. These limits are high enough so that, even with fewer events, the metric values are still representative of your user's app experience.
To manage the volume of data that we collect, Performance Monitoring uses the following sampling options:
On-device rate limiting : To prevent a device from sending sudden bursts of traces, we limit the number of code and network request traces sent from a device to 300 events every 10 mins. This approach protects the device from looped instrumentations that can send large amounts of performance data, and it prevents a single device from skewing the performance measurements.
Dynamic sampling : Performance Monitoring collects a limited number of code traces and network request traces per app daily across all app users. A dynamic sampling rate is fetched on devices (using Firebase Remote Config ) to determine whether a random device should capture and send traces. A device that is not selected for sampling does not send any events. The dynamic sampling rate is app-specific and adjusts to ensure that the overall volume of collected data remains below the limit.
User sessions send additional, detailed data from a user's device, requiring more resources to capture and send the data. To minimize the impact of user sessions, Performance Monitoring might also restrict the number of sessions.
Server-side rate limiting : To ensure that apps don't exceed the sampling limit, Performance Monitoring might use server-side sampling to drop some events received from devices. Although this type of limiting doesn't change the effectiveness of our metrics, it may cause minor pattern shifts, including the following:
- The number of traces can differ from the number of times that a piece of code was executed.
- Traces that are closely coupled in code may each have a different number of samples.
We replaced the Issues tab with the introduction of Alerts, which automatically notifies you when the thresholds you set are exceeded. You no longer need to manually check the Firebase console to determine the status of a threshold. To learn about Alerts, see Set up alerts for performance issues .
We've redesigned the Performance Monitoring section of the Firebase console so that the Dashboard tab displays your key metrics and all your traces in one space. As part of the redesign, we removed the On device and Network pages.
The traces table at the bottom of the Dashboard tab has all the same information that the On device and Network tabs displayed, but with some added features, including the ability to sort your traces by the percentage change for a specific metric. To view all the metrics and data for a specific trace, click the trace name in the traces table.
View your traces in the following subtabs of the traces table:
- Network request traces (both out-of-the-box and custom) — Network requests subtab
- Custom code traces — Custom traces subtab
- App start, app-in-foreground, app-in-background traces — Custom traces subtab
- Screen rendering traces — Screen rendering subtab
- Page load traces — Page load subtab
For details about the traces table and viewing metrics and data, visit the console overview page ( iOS+ | Android | Web ).
Slow rendering frames and frozen frames are calculated with an assumed device refresh rate of 60Hz. If a device refresh rate is lower than 60Hz, each frame will have a slower rendering time because fewer frames are rendered per second. Slower rendering times can cause more slow or frozen frames to be reported because more frames will be rendered slower or will freeze. However, if a device refresh rate is higher than 60Hz, each frame will have a faster rendering time. This can cause fewer slow or frozen frames to be reported. This is a current limitation in the Performance Monitoring SDK.
If Performance Monitoring is the only Firebase product in your app, you can use the standalone Performance Monitoring SDK (and the recommended header script below) if you're interested in:
- using a namespaced library
- reducing your SDK package size
- delaying initialization of the SDK until after your page loads
To include the standalone Performance Monitoring SDK in your app and delay its initialization to after your page loads:
- Add the following script to the header of your index file.
- Make sure to add your app's Firebase project configuration object .
(function(sa,fbc){function load(f,c){var a=document.createElement('script'); a.async=1;a.src=f;var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(a,s);}load(sa); window.addEventListener('load',function(){firebase.initializeApp(fbc).performance()}); })(performance_standalone, firebaseConfig);
где,
- performance_standalone is
'https://www.gstatic.com/firebasejs/12.19.0/firebase-performance.js' - firebaseConfig is your app's Firebase config object
The above script asynchronously loads the standalone SDK then initializes Firebase after the window's onload event fires. This tactic reduces the impact that the SDK could have on page load metrics since the browser has already reported its loading metrics when you initialize the SDK.
You can create up to 400 total custom URL patterns per app and up to 100 custom URL patterns per domain for that app.
Near real-time data processing and display
Firebase Performance Monitoring processes collected performance data as it comes in, which results in near real-time data display in the Firebase console. Processed data displays in the console within a few minutes of its collection, hence the term "near real-time".
To take advantage of near real-time data processing, make sure your app uses a real-time compatible SDK version .
To take advantage of near real-time data processing, you only need to make sure that your app uses a Performance Monitoring SDK version that's compatible with real-time data processing.
These are the real-time compatible SDK versions:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
These are the SDK versions compatible with real-time data processing:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
If your app doesn't use a real-time compatible SDK version, you will still see all your app's performance data in the Firebase console. However, the display of performance data will be delayed by roughly 36 hours from the time of its collection.
Yes! Regardless of which SDK version an app instance uses, you'll see performance data from all your users.
However, if you're looking at recent data (less than roughly 36 hours old), then the displayed data is from users of app instances using a real-time compatible SDK version. The non-recent data, though, includes performance data from all versions of your app.
To view real time performance data, make sure that your app uses a Performance Monitoring SDK version that's compatible with real time data processing.
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
Contacting Firebase Support
If you reach out to Firebase Support , always include your Firebase App ID. Find your Firebase App ID in the Your apps card of your Project settings .
,This page provides troubleshooting tips for getting started with Performance Monitoring or using Performance Monitoring features and tooling.
First checks for troubleshooting
The following two checks are general best practices recommended for anyone before further troubleshooting.
1. Check log messages for performance events
Check your log messages to be sure that the Performance Monitoring SDK is capturing performance events.
Open your browser's developer tools (for example, Network tab for Chrome Dev Tools or in the Network Monitor for Firefox ).
Refresh your web app in the browser.
Check your log messages for any error messages.
After a few seconds, look for a network call to
firebaselogging.googleapis.comin your browser's developer tools. The presence of that network call shows that the browser is sending performance data to Firebase.
If your app isn't logging performance events, review the troubleshooting tips .
2. Check the Firebase Status Dashboard
Check the Firebase Status Dashboard in case there is a known outage for Firebase or for Performance Monitoring .
Getting started with Performance Monitoring
If you're getting started with Performance Monitoring ( iOS+ | Android | Web ), the following troubleshooting tips can help with issues that involve Firebase detecting the SDK or displaying your first performance data in the Firebase console.
Firebase can detect if you've successfully added the Performance Monitoring SDK to your app when it receives event information (like app interactions) from your app. Usually within 10 minutes of starting your app, the Performance dashboard of the Firebase console displays an "SDK detected" message. Then, within 30 minutes, the dashboard displays the initial processed data.
If it's been more than 10 minutes since you added the latest version of SDK to your app, and you're still not seeing any change, check your log messages to make sure that Performance Monitoring is logging events. Try the appropriate troubleshooting steps as described below to troubleshoot a delayed SDK detection message.
If you're still developing locally, try generating more events for data collection:
Serve and view your web app in a local environment.
Generate events by loading subpages for your site, interacting with your app, and/or triggering network requests. Make sure to keep the browser tab open for at least 10 seconds after the page loads.
Make sure that your Firebase configuration object is correctly added to your app and that you haven't modified the object. Specifically, check the following:
- The Firebase Web App ID (
appId) in the config object is correct for your app. Find your Firebase App ID in the Your apps card of your Project settings .
If anything seems wrong with the config object in your app, try the following:
Delete the config object that you currently have in your app.
Follow these instructions to obtain a new config object and add it to your web app.
- The Firebase Web App ID (
If the SDK is logging events and everything seems to be set up correctly, but you're still not seeing the SDK detection message or processed data (after 2 hours), contact Firebase Support .
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Performance Monitoring processes performance event data before displaying it in the Performance dashboard .
If it's been more than 24 hours since the "SDK detected" message appeared , and you're still not seeing data, then check the Firebase Status Dashboard in case there is a known outage. If there is no outage, contact Firebase Support .
Общее устранение неполадок
If you've successfully added the SDK and are using Performance Monitoring in your app, the following troubleshooting tips can help with general issues that involve Performance Monitoring features and tooling.
If you're not seeing log messages for performance events , try the following troubleshooting steps:
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Modern apps omit _fid because Interaction to Next Paint (INP) has replaced First Input Delay (FID).
To record FID in older browsers:
Add the legacy FID polyfill .
Confirm that the user interacts with the page within 5 seconds of load. Performance Monitoring records FID only during this window.
Are you seeing performance data for automatically collected traces but not for custom code traces ? Try the following troubleshooting steps:
Check the setup of custom code traces instrumented via the Trace API , especially the following:
- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
_) character, and max length is 32 characters. - All traces must be started and stopped. Any trace that is not started, not stopped, or stopped before started will not be logged.
Note that if you're using the
record()method, then you don't need to explicitly start or stop your trace.- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
Make sure that Performance Monitoring data collection is not disabled through the following flag:
performance.dataCollectionEnabledThis flag controls the collection of data for custom code traces only (not all data).
Check your log messages to make sure that Performance Monitoring is logging expected custom code traces.
If Performance Monitoring is logging events, but no data displays after 24 hours, contact Firebase Support .
If you're missing network request data, be aware of the following:
Performance Monitoring automatically collects metrics for network requests reported by the browser API. These reports do not include failed network requests.
Depending on the behavior of your code and networking libraries used by your code, Performance Monitoring might only report on network requests that are completed. This means that HTTP/S connections that are left open might not be reported.
Learn more about how Performance Monitoring aggregates network request data under URL patterns.
You can also try out custom URL patterns !
Часто задаваемые вопросы
We replaced Top Issues with Recent Alerts as a follow-up to our recent introduction of alerts, which automatically notify you when the thresholds you set are crossed. Issues are now deprecated and replaced by alerts.
The apps selector at the top of the Performance card filters the alert entries under Recent Alerts . Only the three most recent alerts for the app(s) selected are displayed.
To learn more about alerts, see Set up alerts for performance issues .
Performance Monitoring supports alerts for metrics that exceed defined thresholds. To avoid confusion with these configurable thresholds for performance metrics, we removed the ability to configure thresholds for issues .
We replaced the Details and Metrics pages with a newly redesigned, centralized user interface (UI) to improve how you troubleshoot issues. This new troubleshooting UI offers the same core functionality that Details and Metrics offered. To learn more about troubleshooting, see View more data for a specific trace .
Performance Monitoring collects performance data from your app's user devices. If your application has many users or if the app generates a large amount of performance activity, Performance Monitoring might limit data collection to a subset of devices to reduce the number of processed events. These limits are high enough so that, even with fewer events, the metric values are still representative of your user's app experience.
To manage the volume of data that we collect, Performance Monitoring uses the following sampling options:
On-device rate limiting : To prevent a device from sending sudden bursts of traces, we limit the number of code and network request traces sent from a device to 300 events every 10 mins. This approach protects the device from looped instrumentations that can send large amounts of performance data, and it prevents a single device from skewing the performance measurements.
Dynamic sampling : Performance Monitoring collects a limited number of code traces and network request traces per app daily across all app users. A dynamic sampling rate is fetched on devices (using Firebase Remote Config ) to determine whether a random device should capture and send traces. A device that is not selected for sampling does not send any events. The dynamic sampling rate is app-specific and adjusts to ensure that the overall volume of collected data remains below the limit.
User sessions send additional, detailed data from a user's device, requiring more resources to capture and send the data. To minimize the impact of user sessions, Performance Monitoring might also restrict the number of sessions.
Server-side rate limiting : To ensure that apps don't exceed the sampling limit, Performance Monitoring might use server-side sampling to drop some events received from devices. Although this type of limiting doesn't change the effectiveness of our metrics, it may cause minor pattern shifts, including the following:
- The number of traces can differ from the number of times that a piece of code was executed.
- Traces that are closely coupled in code may each have a different number of samples.
We replaced the Issues tab with the introduction of Alerts, which automatically notifies you when the thresholds you set are exceeded. You no longer need to manually check the Firebase console to determine the status of a threshold. To learn about Alerts, see Set up alerts for performance issues .
We've redesigned the Performance Monitoring section of the Firebase console so that the Dashboard tab displays your key metrics and all your traces in one space. As part of the redesign, we removed the On device and Network pages.
The traces table at the bottom of the Dashboard tab has all the same information that the On device and Network tabs displayed, but with some added features, including the ability to sort your traces by the percentage change for a specific metric. To view all the metrics and data for a specific trace, click the trace name in the traces table.
View your traces in the following subtabs of the traces table:
- Network request traces (both out-of-the-box and custom) — Network requests subtab
- Custom code traces — Custom traces subtab
- App start, app-in-foreground, app-in-background traces — Custom traces subtab
- Screen rendering traces — Screen rendering subtab
- Page load traces — Page load subtab
For details about the traces table and viewing metrics and data, visit the console overview page ( iOS+ | Android | Web ).
Slow rendering frames and frozen frames are calculated with an assumed device refresh rate of 60Hz. If a device refresh rate is lower than 60Hz, each frame will have a slower rendering time because fewer frames are rendered per second. Slower rendering times can cause more slow or frozen frames to be reported because more frames will be rendered slower or will freeze. However, if a device refresh rate is higher than 60Hz, each frame will have a faster rendering time. This can cause fewer slow or frozen frames to be reported. This is a current limitation in the Performance Monitoring SDK.
If Performance Monitoring is the only Firebase product in your app, you can use the standalone Performance Monitoring SDK (and the recommended header script below) if you're interested in:
- using a namespaced library
- reducing your SDK package size
- delaying initialization of the SDK until after your page loads
To include the standalone Performance Monitoring SDK in your app and delay its initialization to after your page loads:
- Add the following script to the header of your index file.
- Make sure to add your app's Firebase project configuration object .
(function(sa,fbc){function load(f,c){var a=document.createElement('script'); a.async=1;a.src=f;var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(a,s);}load(sa); window.addEventListener('load',function(){firebase.initializeApp(fbc).performance()}); })(performance_standalone, firebaseConfig);
где,
- performance_standalone is
'https://www.gstatic.com/firebasejs/12.19.0/firebase-performance.js' - firebaseConfig is your app's Firebase config object
The above script asynchronously loads the standalone SDK then initializes Firebase after the window's onload event fires. This tactic reduces the impact that the SDK could have on page load metrics since the browser has already reported its loading metrics when you initialize the SDK.
You can create up to 400 total custom URL patterns per app and up to 100 custom URL patterns per domain for that app.
Near real-time data processing and display
Firebase Performance Monitoring processes collected performance data as it comes in, which results in near real-time data display in the Firebase console. Processed data displays in the console within a few minutes of its collection, hence the term "near real-time".
To take advantage of near real-time data processing, make sure your app uses a real-time compatible SDK version .
To take advantage of near real-time data processing, you only need to make sure that your app uses a Performance Monitoring SDK version that's compatible with real-time data processing.
These are the real-time compatible SDK versions:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
These are the SDK versions compatible with real-time data processing:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
If your app doesn't use a real-time compatible SDK version, you will still see all your app's performance data in the Firebase console. However, the display of performance data will be delayed by roughly 36 hours from the time of its collection.
Yes! Regardless of which SDK version an app instance uses, you'll see performance data from all your users.
However, if you're looking at recent data (less than roughly 36 hours old), then the displayed data is from users of app instances using a real-time compatible SDK version. The non-recent data, though, includes performance data from all versions of your app.
To view real time performance data, make sure that your app uses a Performance Monitoring SDK version that's compatible with real time data processing.
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
Contacting Firebase Support
If you reach out to Firebase Support , always include your Firebase App ID. Find your Firebase App ID in the Your apps card of your Project settings .
,This page provides troubleshooting tips for getting started with Performance Monitoring or using Performance Monitoring features and tooling.
First checks for troubleshooting
The following two checks are general best practices recommended for anyone before further troubleshooting.
1. Check log messages for performance events
Check your log messages to be sure that the Performance Monitoring SDK is capturing performance events.
Open your browser's developer tools (for example, Network tab for Chrome Dev Tools or in the Network Monitor for Firefox ).
Refresh your web app in the browser.
Check your log messages for any error messages.
After a few seconds, look for a network call to
firebaselogging.googleapis.comin your browser's developer tools. The presence of that network call shows that the browser is sending performance data to Firebase.
If your app isn't logging performance events, review the troubleshooting tips .
2. Check the Firebase Status Dashboard
Check the Firebase Status Dashboard in case there is a known outage for Firebase or for Performance Monitoring .
Getting started with Performance Monitoring
If you're getting started with Performance Monitoring ( iOS+ | Android | Web ), the following troubleshooting tips can help with issues that involve Firebase detecting the SDK or displaying your first performance data in the Firebase console.
Firebase can detect if you've successfully added the Performance Monitoring SDK to your app when it receives event information (like app interactions) from your app. Usually within 10 minutes of starting your app, the Performance dashboard of the Firebase console displays an "SDK detected" message. Then, within 30 minutes, the dashboard displays the initial processed data.
If it's been more than 10 minutes since you added the latest version of SDK to your app, and you're still not seeing any change, check your log messages to make sure that Performance Monitoring is logging events. Try the appropriate troubleshooting steps as described below to troubleshoot a delayed SDK detection message.
If you're still developing locally, try generating more events for data collection:
Serve and view your web app in a local environment.
Generate events by loading subpages for your site, interacting with your app, and/or triggering network requests. Make sure to keep the browser tab open for at least 10 seconds after the page loads.
Make sure that your Firebase configuration object is correctly added to your app and that you haven't modified the object. Specifically, check the following:
- The Firebase Web App ID (
appId) in the config object is correct for your app. Find your Firebase App ID in the Your apps card of your Project settings .
If anything seems wrong with the config object in your app, try the following:
Delete the config object that you currently have in your app.
Follow these instructions to obtain a new config object and add it to your web app.
- The Firebase Web App ID (
If the SDK is logging events and everything seems to be set up correctly, but you're still not seeing the SDK detection message or processed data (after 2 hours), contact Firebase Support .
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Performance Monitoring processes performance event data before displaying it in the Performance dashboard .
If it's been more than 24 hours since the "SDK detected" message appeared , and you're still not seeing data, then check the Firebase Status Dashboard in case there is a known outage. If there is no outage, contact Firebase Support .
Общее устранение неполадок
If you've successfully added the SDK and are using Performance Monitoring in your app, the following troubleshooting tips can help with general issues that involve Performance Monitoring features and tooling.
If you're not seeing log messages for performance events , try the following troubleshooting steps:
Make sure that the Performance Monitoring SDK is correctly initialized in your app.
Make sure that the Performance Monitoring SDK is not disabled through the following flag:
-
performance.instrumentationEnabled
-
Make sure that your browser caching is disabled, otherwise the browser might not pick up any new instrumentation settings.
Close, then reopen the webpage tab. Check for logging again.
If you just added the Performance Monitoring SDK in your app, you might need to fully restart your app for the SDK to start working.
If you can't find anything that's disabled in your app, contact Firebase Support .
Modern apps omit _fid because Interaction to Next Paint (INP) has replaced First Input Delay (FID).
To record FID in older browsers:
Add the legacy FID polyfill .
Confirm that the user interacts with the page within 5 seconds of load. Performance Monitoring records FID only during this window.
Are you seeing performance data for automatically collected traces but not for custom code traces ? Try the following troubleshooting steps:
Check the setup of custom code traces instrumented via the Trace API , especially the following:
- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
_) character, and max length is 32 characters. - All traces must be started and stopped. Any trace that is not started, not stopped, or stopped before started will not be logged.
Note that if you're using the
record()method, then you don't need to explicitly start or stop your trace.- Names for custom code traces and custom metrics must meet the following requirements: no leading or trailing whitespace, no leading underscore (
Make sure that Performance Monitoring data collection is not disabled through the following flag:
performance.dataCollectionEnabledThis flag controls the collection of data for custom code traces only (not all data).
Check your log messages to make sure that Performance Monitoring is logging expected custom code traces.
If Performance Monitoring is logging events, but no data displays after 24 hours, contact Firebase Support .
If you're missing network request data, be aware of the following:
Performance Monitoring automatically collects metrics for network requests reported by the browser API. These reports do not include failed network requests.
Depending on the behavior of your code and networking libraries used by your code, Performance Monitoring might only report on network requests that are completed. This means that HTTP/S connections that are left open might not be reported.
Learn more about how Performance Monitoring aggregates network request data under URL patterns.
You can also try out custom URL patterns !
Часто задаваемые вопросы
We replaced Top Issues with Recent Alerts as a follow-up to our recent introduction of alerts, which automatically notify you when the thresholds you set are crossed. Issues are now deprecated and replaced by alerts.
The apps selector at the top of the Performance card filters the alert entries under Recent Alerts . Only the three most recent alerts for the app(s) selected are displayed.
To learn more about alerts, see Set up alerts for performance issues .
Performance Monitoring supports alerts for metrics that exceed defined thresholds. To avoid confusion with these configurable thresholds for performance metrics, we removed the ability to configure thresholds for issues .
We replaced the Details and Metrics pages with a newly redesigned, centralized user interface (UI) to improve how you troubleshoot issues. This new troubleshooting UI offers the same core functionality that Details and Metrics offered. To learn more about troubleshooting, see View more data for a specific trace .
Performance Monitoring collects performance data from your app's user devices. If your application has many users or if the app generates a large amount of performance activity, Performance Monitoring might limit data collection to a subset of devices to reduce the number of processed events. These limits are high enough so that, even with fewer events, the metric values are still representative of your user's app experience.
To manage the volume of data that we collect, Performance Monitoring uses the following sampling options:
On-device rate limiting : To prevent a device from sending sudden bursts of traces, we limit the number of code and network request traces sent from a device to 300 events every 10 mins. This approach protects the device from looped instrumentations that can send large amounts of performance data, and it prevents a single device from skewing the performance measurements.
Dynamic sampling : Performance Monitoring collects a limited number of code traces and network request traces per app daily across all app users. A dynamic sampling rate is fetched on devices (using Firebase Remote Config ) to determine whether a random device should capture and send traces. A device that is not selected for sampling does not send any events. The dynamic sampling rate is app-specific and adjusts to ensure that the overall volume of collected data remains below the limit.
User sessions send additional, detailed data from a user's device, requiring more resources to capture and send the data. To minimize the impact of user sessions, Performance Monitoring might also restrict the number of sessions.
Server-side rate limiting : To ensure that apps don't exceed the sampling limit, Performance Monitoring might use server-side sampling to drop some events received from devices. Although this type of limiting doesn't change the effectiveness of our metrics, it may cause minor pattern shifts, including the following:
- The number of traces can differ from the number of times that a piece of code was executed.
- Traces that are closely coupled in code may each have a different number of samples.
We replaced the Issues tab with the introduction of Alerts, which automatically notifies you when the thresholds you set are exceeded. You no longer need to manually check the Firebase console to determine the status of a threshold. To learn about Alerts, see Set up alerts for performance issues .
We've redesigned the Performance Monitoring section of the Firebase console so that the Dashboard tab displays your key metrics and all your traces in one space. As part of the redesign, we removed the On device and Network pages.
The traces table at the bottom of the Dashboard tab has all the same information that the On device and Network tabs displayed, but with some added features, including the ability to sort your traces by the percentage change for a specific metric. To view all the metrics and data for a specific trace, click the trace name in the traces table.
View your traces in the following subtabs of the traces table:
- Network request traces (both out-of-the-box and custom) — Network requests subtab
- Custom code traces — Custom traces subtab
- App start, app-in-foreground, app-in-background traces — Custom traces subtab
- Screen rendering traces — Screen rendering subtab
- Page load traces — Page load subtab
For details about the traces table and viewing metrics and data, visit the console overview page ( iOS+ | Android | Web ).
Slow rendering frames and frozen frames are calculated with an assumed device refresh rate of 60Hz. If a device refresh rate is lower than 60Hz, each frame will have a slower rendering time because fewer frames are rendered per second. Slower rendering times can cause more slow or frozen frames to be reported because more frames will be rendered slower or will freeze. However, if a device refresh rate is higher than 60Hz, each frame will have a faster rendering time. This can cause fewer slow or frozen frames to be reported. This is a current limitation in the Performance Monitoring SDK.
If Performance Monitoring is the only Firebase product in your app, you can use the standalone Performance Monitoring SDK (and the recommended header script below) if you're interested in:
- using a namespaced library
- reducing your SDK package size
- delaying initialization of the SDK until after your page loads
To include the standalone Performance Monitoring SDK in your app and delay its initialization to after your page loads:
- Add the following script to the header of your index file.
- Make sure to add your app's Firebase project configuration object .
(function(sa,fbc){function load(f,c){var a=document.createElement('script'); a.async=1;a.src=f;var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(a,s);}load(sa); window.addEventListener('load',function(){firebase.initializeApp(fbc).performance()}); })(performance_standalone, firebaseConfig);
где,
- performance_standalone is
'https://www.gstatic.com/firebasejs/12.19.0/firebase-performance.js' - firebaseConfig is your app's Firebase config object
The above script asynchronously loads the standalone SDK then initializes Firebase after the window's onload event fires. This tactic reduces the impact that the SDK could have on page load metrics since the browser has already reported its loading metrics when you initialize the SDK.
You can create up to 400 total custom URL patterns per app and up to 100 custom URL patterns per domain for that app.
Near real-time data processing and display
Firebase Performance Monitoring processes collected performance data as it comes in, which results in near real-time data display in the Firebase console. Processed data displays in the console within a few minutes of its collection, hence the term "near real-time".
To take advantage of near real-time data processing, make sure your app uses a real-time compatible SDK version .
To take advantage of near real-time data processing, you only need to make sure that your app uses a Performance Monitoring SDK version that's compatible with real-time data processing.
These are the real-time compatible SDK versions:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
These are the SDK versions compatible with real-time data processing:
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
If your app doesn't use a real-time compatible SDK version, you will still see all your app's performance data in the Firebase console. However, the display of performance data will be delayed by roughly 36 hours from the time of its collection.
Yes! Regardless of which SDK version an app instance uses, you'll see performance data from all your users.
However, if you're looking at recent data (less than roughly 36 hours old), then the displayed data is from users of app instances using a real-time compatible SDK version. The non-recent data, though, includes performance data from all versions of your app.
To view real time performance data, make sure that your app uses a Performance Monitoring SDK version that's compatible with real time data processing.
- iOS — v7.3.0 or later
- tvOS — v8.9.0 or later
- Android — v19.0.10 or later (or Firebase Android BoM v26.1.0 or later)
- Web — v7.14.0 or later
Note that we always recommend using the latest version of SDK, but any version listed above will enable Performance Monitoring to process your data in near real time.
Contacting Firebase Support
If you reach out to Firebase Support , always include your Firebase App ID. Find your Firebase App ID in the Your apps card of your Project settings .