If you add or
edit a custom probe, the custom probe wizard
is displayed. In several steps, it leads you through the creation of a custom probe.
You can directly jump to
another step of the wizard by clicking on the step in the index. The wizard is partitioned
into the following steps:
ProbeMetaData#create(String)
and the description is set with
ProbeMetaData#description(String)
. This could be set in the meta data script in the next step,
but since JProfiler needs to display this information in the custom probe configuration,
it is entered separately
outside the script and applied to the ProbeMetaData
object before it is passed to the meta data script.
metaData
of type ProbeMetaData
and does not return anything.
New probes contain a non-functional example script that gives you a starting point
for your own configuration.
ProbeContext
and an int-array with the data to be filled.
To retrieve data that was collected during interceptions, you have to use the map
returned by probeContext.getMap()
.
The n-th index in the int-array corresponds to the n-th telemetry that was defined
in the meta-data script.
The context menu for the list of methods offers the option to edit existing entries.
InterceptorContext
(which is
an extension of ProbeContext
) and the current object currentObject
(which is null
for static method interceptions).
There are interception scripts for three points in the execution flow:
t
is passed as a parameter. The method exit script
will not be called in this case.
Interception scripts must be defined separately for each method group.
To automatically add a set of custom probe to new sessions, configure a saved custom probe set on the session defaults tab of the general settings dialog.
To share a set of custom probes with a colleague, or to copy it to another JProfiler installation, use the import/export feature.