The number of cache hits and misses or the number of times that the UI becomes For example, you can create a custom metric for
ITRACE EXAMPLE CODE
You can further configure a custom code trace to recordĬustom metrics for performance-related events that (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 The module, whenever an inclusion directive was automatically turned into a module import or null otherwise.Performance Monitoring collects traces to help you monitor the performance of your app.
The path relative to SearchPath, at which the include file was found. The actual file that may be included by this inclusion directive.Ĭontains the search path which was used to find the file in the file system. The character range of the quotes or angle brackets for the written file name. Whether the file name was enclosed in angle brackets otherwise, it was enclosed in quotes. The name of the file being included, as written in the source code. The token that indicates the kind of inclusion directive, e.g., ‘include’ or ‘import’. The location of the ‘#’ that starts the inclusion directive. InclusionDirective is called when an inclusion directive of any kind (#include, #import, etc.) has been processed, regardless of whether the inclusion will actually result in an inclusion. Instead of trying to display all members of the structure. Value, only some key member or members are shown to represent the value,
Note that in some cases, such as when a structure pointer is an argument The description describes the argument or what is displayed for it. The Clang C++ Type field is the type from the callback function declaration. Locations are shown as quoted only to avoid confusing the documentation generator. It might be a literal, such as (null), for a null pointer. A name in parenthesesĬan either represent a place holder for the described value, or confusingly, Enumeration member symbols are shown as theĪctual enum member in a (member1|member2|…) form. It uses an ad hoc representation that mixes literalĪnd symbolic representations. The Argument Value Syntax field describes the values that will be displayedįor the argument value. The Argument Name field in most (but not all) cases is the same name as the
The argument descriptions table describes the callback argument information The following sections describe the purpose and output format for each callback.Ĭlick on the callback name in the section heading to see the Doxygen
0 kommentar(er)
