The probe
The probe is a utility that captures detailed diagnostic and state information about transactions that a service processes.
The probe displays the contents of processing contexts and displays the value of variables at each processing step in a processing rule. A processing rule might contain one or more processing steps. The probe can be an invaluable tool during service development.
The DataPower® Gateway provides the following probes where each has a
different setup and each is independent.
- New UI and new probe
- The new probe captures transaction data for DataPower services. The captured data is distributed to peer members by using the gateway-peering instance that is defined in probe settings. To capture transaction data, you must open the new probe and define capture settings.
- WebGUI and traditional probe (deprecated)
- The traditional probe captures transaction data for DataPower services. Except for the B2B gateway and web token service, you can define triggers. Triggers enable the capture of data for only transactions that match specific criteria.
Attention: When you click Show probe, the probe that is
specific to that GUI opens.
- The new probe cannot display data for transactions that the traditional probe captured.
- The traditional probe cannot display data for transactions that the new probe captured.
Although the DataPower Gateway provides global commands and REST actions to
capture transaction data for the API gateway, the DataPower Gateway provides no
utility to view this data.
Note: To debug APIs that an API gateway processes, use the
Test tab in API Designer or API Manager of API Connect.
After the new or traditional probe captures transaction data, the way you work with the captured data for each transaction is similar. The primary difference between these probes is that the new probe provides a side-by-side view to analyze the input and output data for each processing action.