To use this API, you need either a Browser Pro or Pro+SPA edition of the browser agent.
newrelic.addRelease(string $release_name, string $release_id)
Agent version nr-1016 or higher.
In browser monitoring, a release is a way to tag errors with information about what version of your application is currently running. This is useful for sites where shared components are owned by different teams, or multiple applications are deployed independently but run on the same page.
Modern web applications have many interconnecting parts, so an application may have multiple releases (with different names) associated with the same page load. For example, you can use releases to:
- See differences between errors from an old cached version of your app and errors coming from a new version.
- Identify problems found during A/B testing, slow rollouts, feature flags, and other advanced deployment methods.
- Determine which version of a browser source map to use.
git commit sha in the filename of the deployed code. These are enough to uniquely determine the release that caused the error.
As soon as possible after your page loads, call
Required. A short description of the component; for example, the name of a project, application, file, or library.
Required. The ID or version of this release; for example, a version number, build number from your CI environment, GitHub SHA, GUID, or a hash of the contents. Since New Relic converts this value into a string, you can also use
newrelic.addRelease('checkout page', 'a818994')