Enabling RUM/Client Support in separate application

[DannyDouglass]

The documentation shows how to enabled tracking for client application reporting when that client app is served by the Node app. In my situation I have a Node API application hosted in a different app/location (Heroku) and an Angular application (Amazon S3). How would I enabled support for RUM on the client in that scenario?

[groundwater]

Hi @DannyDouglass, our awesome browser agent team would definitely like to support this, but unfortunately there is no standalone version of the browser tracer available at this time.

Traces must be generated in the server module, if you can somehow insert the results of newrelic.getBrowserTimingHeader() into the angular app that might work, but that is definitely an unsupported use case.

I definitely like your separation of concerns design, it looks like a solid approach. It's just non-standard enough that our tooling doesn't really address that approach yet. I'm going to close this issue because it's unlikely to be solved in the node module, but rather as a new product offering.

My best suggestion is to email support@newrelic.com and register your interest in this feature. It will help prioritize it against other feature requests, and you can get notified directly if and when we roll something like this out.