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.com
in 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.
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 this detection message, 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 (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.
General troubleshooting
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.
If you're not seeing data for the first input delay metric, try the following troubleshooting steps:
Be aware that Performance Monitoring only records the first input delay metric when a user clicks on the web page within the first 5 seconds after page load.
Make sure that you've set up your app to measure this metric. The first input delay metric requires manual setup. Specifically, you need to add the polyfill library for this metric. For installation instructions, refer to the library's documentation.
Note that adding this polyfill library is not required for Performance Monitoring to report other web app metrics.
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.dataCollectionEnabled
This 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!
FAQ
Near real time data processing and display
Firebase Performance Monitoring is enhancing its data processing capabilities to reduce the processing latency for collected performance data. The performance data displayed in the Firebase console will soon reflect "near real time" data (meaning a few minutes delay for data display).
Previously, we processed collected performance data in batches, which resulted in a gap of a few hours between data collection and its display in the console. We're now processing the collected data as it comes in, which results in more immediate data display.
To take advantage of near real time data processing (when it fully launches), make sure your app uses a real time compatible SDK version.
To take advantage of near real time data processing (when it fully launches), 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
- 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
- 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, after real time data processing fully launches, 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.
Note that after real time data processing fully launches, there will be some differences. After the full launch, if you look 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.
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.