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

Stop browser APP sending metricts #719

Open
Khaos93 opened this issue Sep 19, 2023 · 7 comments
Open

Stop browser APP sending metricts #719

Khaos93 opened this issue Sep 19, 2023 · 7 comments
Labels
enhancement New feature or request

Comments

@Khaos93
Copy link

Khaos93 commented Sep 19, 2023

Hi

I want to know if is there a method or mechanism available to intentionally halt the browser agent from sending metricts to New Relic

@Khaos93 Khaos93 added the enhancement New feature or request label Sep 19, 2023
@workato-integration
Copy link

@patrickhousley
Copy link
Member

Hi @Khaos93 can you elaborate more on what data you are not wanting to send and what your current installation/implementation of the browser agent looks like?

@Khaos93
Copy link
Author

Khaos93 commented Sep 19, 2023

Hi @patrickhousley

I have an application embedded within other client applications. The issue I'm encountering is that when the embedded app is unmounted within the parent application, the New Relic client continues to send metrics even though the initializing application is no longer active.

agent = new MicroAgent({ configuration }) agent.start

we are using the verion 1.238.0

@patrickhousley
Copy link
Member

@Khaos93 I know this might be a tough ask but is there any way you could create a simple app to highlight this use-case for us? You can zip up the source and drop it here.

@workato-integration
Copy link

@FranciscoKloganB
Copy link

FranciscoKloganB commented Feb 28, 2024

An explicit stop feature is also desired by us in the browser agent.

We are allowing the user to opt-in to instrumentation and session replay.

We explicit call the start on the after he opts-in and we would like to call stop if he opts out. Currently, our work around is to start with a minimum set of autoStart: true features, with the rest being autoStart: false. When the user opts-out we reload the window, but the user might lose saved work with this approach.

@edelgado
Copy link

edelgado commented Apr 6, 2024

+1 I'd love to be able to disable features from the running instance of the agent: window.newrelic.

I tried adding new keys to window.newrelic.init like:

window.newrelic.init.spa = {enabled: false};

But that seems to have no effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants