Apigee shared proxy dynamic name is not getting resolved by newrelic

[xaraju]

Apigee shared proxy dynamic name is not getting resolved by newrelic

Description

We have added the .js files for enabling the distributed tracing and created a shared proxy in apigee. Once the shared proxy is being used from other api proxies, the dynamic name variable is not being resolved while recording the traces in newrelic.
The data is displayed under same variable name and not the different api proxy names.
NOTE: # ( Describe the problem you're encountering. )
[TIP]: # ( Do NOT give us access or passwords to your New Relic account or API keys! )

Steps to Reproduce

Add the .js files for apigee distributed tracing in a shared apige proxy. Add the shared proxy in multiple api proxy work flows.
But when we try to add a dynamic variable in ‘RequestResponsePairName’ as ‘apiproxy.name’ as shown in attachment config1.
Apigee is able to resolve this variable, but when it reaches new relic, the variable is not resolved and populated variable name

Expected Behavior

The dynamic api names will get resolved in newrelic and traces of different apis will show under different transactions.
NOTE: # ( Tell us what you expected to happen.)

Relevant Logs / Console output

Your Environment

perf
[TIP]: # ( Include as many relevant details about your environment as possible. )

• ex: Browser name and version:
• ex: Operating System and version:

Additional context

[msummers-nr]

RequestResponsePairName is a string literal, there is no environment substitution. It is not similar to TraceStartTimestamp

To change this we'd have to modify the JS code to test for the value in the environment and deal with a null/empty result.