Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling RUM/Client Support in separate application #126

Closed
DannyDouglass opened this issue Mar 15, 2014 · 1 comment
Closed

Enabling RUM/Client Support in separate application #126

DannyDouglass opened this issue Mar 15, 2014 · 1 comment

Comments

@DannyDouglass
Copy link

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
Copy link
Contributor

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 [email protected] 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.

bizob2828 pushed a commit to bizob2828/node-newrelic that referenced this issue Apr 19, 2024
…040ce2b72237fec9264bb8

[Snyk] Upgrade newrelic from 8.7.0 to 8.7.1
bizob2828 pushed a commit to bizob2828/node-newrelic that referenced this issue Apr 23, 2024
…040ce2b72237fec9264bb8

[Snyk] Upgrade newrelic from 8.7.0 to 8.7.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants