Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
At a glance
Goal: Record and export Dev Proxy activity to a report file
Time: 10 minutes
Plugins: ExecutionSummaryPlugin, MarkdownReporter
Prerequisites: Set up Dev Proxy
To record and export proxy activity, use the ExecutionSummaryPlugin and a reporter plugin in your configuration file.
The following example shows how to configure the Dev Proxy to record and export proxy activity using the ExecutionSummaryPlugin and the MarkdownReporter plugin.
File: devproxyrc.json
{
"plugins": [
{
"name": "ExecutionSummaryPlugin",
"enabled": true,
"pluginPath": "~appFolder/plugins/DevProxy.Plugins.dll"
},
{
"name": "MarkdownReporter",
"enabled": true,
"pluginPath": "~appFolder/plugins/DevProxy.Plugins.dll"
}
],
"urlsToWatch": [
"https://jsonplaceholder.typicode.com/*"
]
}
Note
To export the activity, the reporter plugin must be enabled in the configuration file and placed after the ExecutionSummaryPlugin in the plugins list. It is recommended to place a reporter plugin at the end of the plugins list.
To record activity, Dev Proxy must be placed in record mode.
There are two ways to start recording:
- Record immediately. Start proxy with
--recordoption, for example,devproxy --record. - Record adhoc. Press R while proxy is running.
When recording is enabled, ? Recording... is shown in the proxy output.
To generate a report from the recorded activity, stop recording.
There are two ways to stop recording:
- Stop proxy. Press Ctrl + C.
- Stop adhoc. Press S.
By default, activities grouped by URL. To group activity by message type, use the --summary-group-by option.
devproxy --record --summary-group-by messageType
Note
All recording is local. No data is sent to Microsoft.
See also
- ExecutionSummaryPlugin - Full reference
- MarkdownReporter - Report format
- Glossary - Dev Proxy terminology