By default, when you start probe recording, event recording is not enabled. While the probe always processes all events, in this mode it discards them immediately after updating the higher-level measurements in order to minimize overhead. For example, a non-trivial compound file operation will quickly accumulate several hundred thousand single events.
There is a separate recording button in the events view whose state corresponds to the "Record single events" check box in the probe settings. The state of the button is persistent, so if you start event recording once, it will be automatically be started for the next session.
For custom probes, call metaData.events(true)
in the meta data script
to enable event recording.
At the bottom the of the table, there is a special total row that sums all summable columns in the table. For the default columns this only includes the "Duration" column, Together with the filter selector described below, you can analyze the collected data for selected subsets of events.
Below the main table, the call stack of the selected event is shown. This is the call stack of the payload and forms the basis of the hot spot calculation.
By default, the filter works on all available columns. In order to be more specific, you can select a particular column from the "Filter by" drop-down list. This is useful, for example, to show a control object with a particular ID without getting spurious matches from other columns.