For Infinite Tracing, you can supply an optional proxy configuration if outbound traffic needs to flow through a proxy before reaching a trace observer. The language agents that support this are listed below.
In order for a proxy to work with Infinite Tracing, it needs to support the HTTP/2 protocol rather than standard HTTP/1.1. Consult your proxy documentation to determine if this support is available.
Specify the proxy address with the environment variables
NO_PROXY (or their corresponding lowercase versions).
The Java agent gRPC implementation automatically uses the standard JVM proxy properties as noted in the Java Networking Properties documentation. An example system property configuration may look like this:
If your application is already using a proxy, these properties may already be set, in which case gRPC should automatically route Infinite Tracing data through the proxy.
.Net is not supported.
The proxy address can be specified by the environment variables
HTTP_PROXY. These variables are checked in order, and the first one that has a value is used.
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.