[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-24 (世界標準時間)。"],[],[],null,["Firebase Performance Monitoring \nplat_ios plat_android plat_web plat_flutter \nGain insight into your app's performance issues. \nFirebase Performance Monitoring is a service that helps you to gain insight into the performance characteristics of your Apple, Android, and web apps.\n\n\u003cbr /\u003e\n\nYou use the Performance Monitoring SDK to collect performance data from your app, then\nreview and analyze that data in the Firebase console. Performance Monitoring helps you\nto understand in real time where the performance of your app can be improved so\nthat you can use that information to fix performance issues.\n\n\u003cbr /\u003e\n\nReady to get started? Choose your platform:\n\n[iOS+](/docs/perf-mon/get-started-ios)\n[Android](/docs/perf-mon/get-started-android)\n[Web](/docs/perf-mon/get-started-web)\n[Flutter](/docs/perf-mon/flutter/get-started)\n\nKey capabilities\n\nHow does it work?\n\nWhen you add the Performance Monitoring SDK, Firebase *automatically* starts collecting\ndata for several common processes in your app, for example:\n\nPerformance Monitoring uses ***traces*** to collect data about these processes. A trace is\na report that contains data captured between two points in time in your app.\n\nThe collected performance data for each trace are called ***metrics*** and vary\ndepending on the type of trace. For example, when an instance of your app issues\na network request, the trace collects metrics that are important for network\nrequest monitoring, like response time and payload size.\n\nEach time an instance of your app runs a monitored process, the associated trace\nalso automatically collects ***attributes*** data for that app instance. For\nexample, if an Android app issues a network request, the trace collects the\ndevice, app version, and other attributes for that specific app instance. You\ncan use these attributes to filter your performance data and learn if specific\nuser segments are experiencing issues.\n\nThe out-of-the-box traces from Performance Monitoring get you started with monitoring your\napp, but to learn about the performance of specific tasks or flows, try out\n[instrumenting your own custom traces of code](/docs/perf-mon/custom-code-traces)\nin your app.\n\nImplementation path\n\nUser data\n\nPerformance Monitoring does not permanently store any personally identifiable\ninformation (such as names, email addresses, or phone numbers). While monitoring\nHTTP network requests, Performance Monitoring uses URLs (not including URL parameters)\nto build aggregated and anonymous URL patterns that are eventually persisted\nand shown in the Firebase console.\n\nFor more details, refer to the\n[Examples of information collected by\nPerformance Monitoring](/support/privacy#performance-monitoring-collected-info).\n\nNext steps\n\n- To get started using Performance Monitoring in your app, visit:\n\n - [Get Started with Performance Monitoring for Apple platforms](/docs/perf-mon/get-started-ios)\n - [Get Started with Performance Monitoring for Android](/docs/perf-mon/get-started-android)\n - [Get Started with Performance Monitoring for web](/docs/perf-mon/get-started-web)\n - [Get Started with Performance Monitoring on Flutter](/docs/perf-mon/flutter/get-started)\n- To learn about setting up alerts, see [Set up alerts for performance issues](https://firebase.google.com/docs/perf-mon/alerts)."]]
