New Relic allows you to collect standard HTTP parameters, as well as custom parameters, with every transaction trace, browser trace, and error. For example, you may want to track the user name associated with a slow or failing request.
Request parameters are associated with specific transaction traces, browser traces, and errors. You can see the parameters recorded with a request when viewing the individual trace or error.
The New Relic agent can collect the HTTP parameters sent with a request. For example, the key-value pair
name : Bob would be reported for a request to
http://example.com/index.php?name=Bob. These parameters will appear under Request parameters when you view a transaction trace, browser trace, or error.
To enable HTTP parameter collections (if available):
You can specify your own key-value pairs that will be associated with a slow or failing request. Anywhere in the code that handles a web transaction in your application, call an API provided by the New Relic agent. For more information, refer to the documentation for your agent:
Additional documentation resources include:
If you still have problems, submit a support ticket (for fastest service) or email support @ New Relic. Also, you may be able to find support from the community at Stack Overflow. Tag your post with