Read on to learn about synthetic monitoring's proxy settings and properties.
You can set proxy server configuration for synthetic scripted monitors for monitor versions 0.4.0 or higher.
The global object
$network allows you to control the network configuration used by your synthetic scripted monitors. The following are applicable for both scripted browsers and API tests, unless otherwise stated.
This proxy information applies only to these versions:
- API monitors: 0.4.0, 0.2.2, 0.2.1, 0.1.0
- Scripted monitors: 0.1.0
In order to analyze and collect your HTTP traffic metrics, New Relic must ensure the traffic passes through a conceptual funnel. Our synthetic monitoring includes a software funnel component capable of analyzing the HTTP requests or responses and then recording the information.
- New Relic's scripted browser monitors (versions 0.4.x and lower) include a mechanism to do this analysis without needing an HTTP proxy, so you don't have to configure anything.
- New Relic's API test (versions 0.4.x and lower) provides an
$httpobject that is pre-configured to make the requests pass through the internal HTTP proxy. This allows you to write your test without including any proxy settings.
If you want to use some other way to generate HTTP traffic while still collecting the HTTP traffic metrics, you can use
$env.PROXY_PORT. To record traffic metrics, be sure to include these properties in your script.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.