noticeError on the MicroAgent doesn't fire any errors

[cormaclc]

Description

It seems that in any version > 1.289.0 calling noticeError() on any instance of the micro agent doesn't fire an error.

Steps to Reproduce

Instantiate a micro agent (new MicroAgent(...)). Call the noticeError(...) method on that micro agent. Notice that no data comes through to the new relic app and no network calls can be observed in the console.

Expected Behavior

When calling noticeError() on the micro agent I would expect to see an error come through in the browser app.

Your Environment

Any version of the agent > 1.289.0. 1.289.0 appears to be last version where noticeError() still works as expected.

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-426413

[metal-messiah]

Thanks for repoting this @cormaclc . Looking into this now

[metal-messiah]

Hi @cormaclc I tried to replicate this behavior locally but couldn't, both from the distribution of the MicroAgent class as well as the source code.

Would you be able to share some information about your build to help us understand the issue you are facing? If you have a public-facing web application this is occurring on, that is also often helpful!

[jedwardspalisade]

@metal-messiah we too are having issues with noticeError() not firing an alert within New Relic.

We are on version 1.293.0 and using it directly on the BrowserAgent instance but can confirm the same instance is alerting ok for uncaught errors.

[metal-messiah]

Hi @jedwardspalisade , if possible are you able to share any replication information about your implementation? We are not seeing this issue locally and that would help us narrow in on what is happening.

[michael-wynne]

Hi @metal-messiah, I'm similarly seeing that noticeError doesn't work for agents > 1.289.0. In fact, when watching the network closely, I can see that noticeError does not fire a network request. I followed the docs pretty directly; instantiated the agent and tried calling noticeError. There were no signs of failure, just no network request was generated.

Anecdotally, I needed to avoid webpack emitting extra chunks for newrelic code, so I'm importing like this const NewRelic = require('@newrelic/browser-agent/loaders/micro-agent'). In my testing, it seemed like noticeError was working fine when using a normal ESM import, just the CJS imported code that wasn't working. Bumping the version back down to 1.289.0 fixed the issue. Hope this helps!

[metal-messiah]

Seeing that the version mentioned here matches the version issue in #1547, tying these together for now to see if new changes for that issue help resolve this issue. Will follow up with thread participants when that change goes live

[jedwardspalisade]

@metal-messiah For info, and incase it helps, I've been doing some more work this week on our New Relic integration. I narrowed our issue down to the fact we were storing the BrowserAgent in a context variable. E.g.

const browserAgent = new BrowserAgent(options);

browserAgent.noticeError(...);

I believe, from the docs, that this should be possible. I could see window.newrelic initiated within the browser console and could also see the NRBR network requests being made and wrapped console logs, but nothing reporting in NR.

[metal-messiah]

Thanks @jedwardspalisade

Are you able to confirm if calling newrelic.<api> worked as expected vs the variable reference you shared in the example? When you say you saw the NRBR requests being made, are you referring to requests made to a URL like ...bam.nr-data... and do those requests look like they contain the correct license-key and app ID information?