![]() (such as, game level or user properties). YouĬan also add and monitor custom attributes So that you can filter the data for the trace in the Firebase console. (common metadata like app version, country, device, etc.) Default attributes, custom attributes, and custom metricsįor custom code traces, Performance Monitoring automatically logs You should avoid creating custom code traces at high frequencies (for example, Note: Starting and stopping traces too rapidly can be resource intensive, so Table, which is at the bottom of the Performance dashboard (learn more about You can view data from these traces in the Custom traces subtab of the traces Since the default metric collected for these traces is "duration", they are The APIs provided by the Performance Monitoring SDK.Ĭustom code traces can be started anytime after they've been created, and they In your code, you define the beginning and the end of a custom code trace using The starting and stopping points of the trace), but you can add The default metric for a custom code trace is its "duration" (the time between ![]() ![]() Long it takes your app to complete a specific task or a set of tasks, forĮxample loading a set of images or querying your database. With a custom code trace, you can measure how You can create your own traces to monitor performance data associated with Trace is a report of performance data captured between two points in time in Performance Monitoring collects traces to help you monitor the performance of your app.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |