New Relic limitations

Limitations to the behavior and options of the New Relic Integration on a VIP Platform environment:

• When activated, New Relic samples 10% of requests to an environment. It is possible that activating New Relic for an environment will lead to an increase in CPU and memory usage by about 10% on traced requests for some applications.
• No New Relic account other than WordPress VIP’s can be configured for an environment. Only licenses from VIP’s New Relic account can be used for applications hosted on the VIP Platform. This ensures that the VIP team has access to an environment’s New Relic dashboard to perform any analyses or investigations required to support customer sites.
• Configuring a New Relic agent to report data from outside of the VIP Platform to the VIP-provided New Relic account is not allowed. Any data originating outside of the VIP Platform will be blocked without warning.
• New Relic may not be supported by the most recent PHP version if it is currently in “testing”. To be able to use New Relic, use a version of PHP included in New Relic’s PHP agent compatibility list by setting the PHP Version for the environment in the VIP Dashboard.
• Due to the possibility of exposing private attributes of requests, some of the query parameters are intentionally obfuscated in New Relic’s UI. In those cases, some values will be represented by question marks or no query params in traces or database queries will appear. Some of these can be selectively re-enabled, but with great caution. Only allow the values of query parameter keys that are always innocuous.