newrelic / nr1-browser-analyzer

NR1 Browser Analyzer allows you to understand the impact and performance of your website.

New Relic Browser Analyzer

Usage

Using the Apdex score generated by Browser's PageView event, Browser Analyzer displays an analysis of performance, and forecasts how performance improvements can impact Key Performance Indicators, like bounce rate or traffic.

This application allows you to explore the performance of individual site pages, and identifies improvement opportunities by showing which pages have the worst performance impact, allowing you to target high-impact fixes.

Dependencies

Requires New Relic Browser.

Enabling this App

This App is available via the New Relic Catalog.

To enable it in your account, go to Add Data > Apps and Visualzations and search for "Browser Analyzer". Click the card, and then click the "Add this App" button to add it to your account(s).

Once subscribed:

1. navigate to a Browser app via the Entity Explorer in New Relic One
2. locate the "Site Analyzer" menu item in the secondary left-nav, found under "More Views"
3. click "Site Analyzer" to open the app (note: on the first time accessing the app, you may be prompted to enable it)

Manual Deployment

If you need to customize this application, you can fork the codebase and follow the instructions on how to Customize a Nerdpack. If you have a change you feel everyone can benefit from, please submit a PR!

Support

This project is actively maintained by the New Relic Labs team. Connect with us directly by creating issues or asking questions in the discussions section of this repo.

We also encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

New Relic has open-sourced this project, which is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT.

Security

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals. If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

Contributing

Contributions are welcome; please review our Contributors Guide.

Keep in mind that when you submit a pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at [email protected].

Open Source License

This project is distributed under the Apache 2 license.

nr1-browser-analyzer's Issues

Apdex T value not being acknowledged, falls back to default (0.5) instead

Description

For some reason our deployment of "Browser Analyzer" on our Browser app is not acknowledging the Apdex T value correctly and instead is just taking the default Apdex T value of "0.5", hence the metrics displayed are not accurate

Steps to Reproduce

Our Apdex T value:

Instead, Site Analyzer is considering the default Apdex T value of 0.5:

This Browser app is still running a fairly old version of the Browser agent (1071), so not sure that is the reason. Is there a minimum required Browser agent version required for the correct Apdex T value to be acknowledged?

All instances of the Fira Sans font are displaying as times new roman

Fira Sans is never actually pulled in as a font and it's not included by default in NR1.

Hint, hint: @import url('https://fonts.googleapis.com/css?family=Fira+Sans:300,400,400i,600&display=swap');

[Repolinter] Open Source Policy Issues

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

❗ Error	❌ Fail	⚠️ Warn	✅ Pass	Ignored	Total
0	1	0	12	0	13

• Fail
  • ❌ code-of-conduct-file-does-not-exist
• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-starts-with-nr1-catalog-header
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ readme-contains-discuss-topic
  • ✅ third-party-notices-file-exists
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists
  • ✅ package-scripts-present

Fail #

❌ code-of-conduct-file-does-not-exist #

New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Found files. Below is a list of files or patterns that failed:

• CODE_OF_CONDUCT.md
  • 🔨 Suggested Fix: Remove file

Passed #

Click to see rules

✅ license-file-exists #

Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.

✅ readme-file-exists #

Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.

✅ readme-starts-with-nr1-catalog-header #

The first 1 lines contain all of the requested patterns. (README.md). The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/.

✅ readme-contains-security-section #

Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-link-to-security-policy #

Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-discuss-topic #

Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ third-party-notices-file-exists #

Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ github-actions-workflow-file-exists #

Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ nr1-catalog-config-file-exists #

Found file (catalog/config.json).

✅ nr1-catalog-screenshots-directory-exists #

Found file (catalog/screenshots).

✅ nr1-catalog-documentation-file-exists #

Found file (catalog/documentation.md).

✅ package-scripts-present #

An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.

Update eslint

sudo rm -r node_modules
npm uninstall eslint
npm install --save-dev eslint

Update package dependencies

Down Stream Drill Down functionality for Browser Analyzer

High Overview

Customer would like the capability to jump to downstream drill down from the Browser Analyzer Nerdlet similar to the upstream capabilities for deep dive into APM. In other words, customer would like to see which specific end user clients or versions or geo's are impacting scores or performance.

Summary of new Feature

Provide mechanism that a customer can filter on the front end metrics to help identify which clients are experiencing 'bad' APDEX scores or Performance.

Desired Behaviour

Provide link to Browser Filterable Geography or capability to filter on End User attributes to allow filtering on front end metrics (example, Desktop, Table, Mobile Web or GEO locations or Browser Versions, etc).

Possible Solution

See Above

Additional context

I believe this is important feature request since this particular Nerdlet links downstream to APM but has not functionality to isolate upstream client details.

Custom Date Range Displays Error in Site Analyzer

When using Site Analyzer, if you use a Custom Date range from the date picker, the tool gives an error. The Site Analyzer seems to only work with the pre-defined date ranges in the drop down. See the attached screenshot of the error.

Check the icons for sizing issues

I believe the latest changes in NR1 adjusted some assumption w/r/t the colored icons on the page. It's worth a visual inspection by a visual expert.

Upgrade the UX for the empty state

When one navigate to an entity that doesn't have access to the Nerdlet, one encounters the following:

That should move to the NR1 Community EmptyState.

[Repolinter] Open Source Policy Issues

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

❗ Error	❌ Fail	⚠️ Warn	✅ Pass	Ignored	Total
0	2	0	11	0	13

• Fail
  • ❌ readme-starts-with-nr1-catalog-header
  • ❌ readme-contains-forum-topic
• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ third-party-notices-file-exists
  • ✅ code-of-conduct-should-not-exist-here
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists
  • ✅ package-scripts-present

Fail #

❌ readme-starts-with-nr1-catalog-header #

The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/. Below is a list of files or patterns that failed:

• README.md: The first 1 lines do not contain the pattern(s): Open source NR1 Catalog header (see https://opensource.newrelic.com/oss-category).
  • 🔨 Suggested Fix: prepend the latest code snippet found at https://github.com/newrelic/opensource-website/wiki/Open-Source-Category-Snippets#code-snippet-3 to file

❌ readme-contains-forum-topic #

Doesn't contain a link to the appropriate forum.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate forum.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

Passed #

Click to see rules

✅ license-file-exists #

Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.

✅ readme-file-exists #

Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.

✅ readme-contains-security-section #

Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-link-to-security-policy #

Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ third-party-notices-file-exists #

Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ code-of-conduct-should-not-exist-here #

New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Did not find a file matching the specified patterns. All files passed this test.

✅ github-actions-workflow-file-exists #

Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ nr1-catalog-config-file-exists #

Found file (catalog/config.json).

✅ nr1-catalog-screenshots-directory-exists #

Found file (catalog/screenshots).

✅ nr1-catalog-documentation-file-exists #

Found file (catalog/documentation.md).

✅ package-scripts-present #

An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.

Site Analyzer shows "Oops! Something went wrong." on a brand new New Relic account

Description

Created a brand new account on New Relic and took all the necessary steps to install java script based Site Analyzer from the New Relic global catalog. Everything was working fine the first day. Came back to the console the next day, and all I can see is this message "Oops! Something went wrong."

Steps to Reproduce

Expected Behaviour

I should be able to see graphs and other info as I did the first day.

Relevant Logs / Console output

Your Environment

• NR1 CLI version used:
• Browser name and version: Tried both Brave (Version 1.15.72 Chromium: 86.0.4240.75 (Official Build) (x86_64)) and Firefox (81.0.1 (64-bit)) browsers
• Operating System and version: MacOS Catalina (10.15.7 (19H2))

Additional context

Top Performance Improvement Targets links to a new tab

Description

The links in that table go to new tabs. It should not. The link within the table should just open a new Stacked nerdlet and allow you to click on the link in that Nerdlet to open the new tab.

Steps to Reproduce

• Navigate to the Nerdlet
• Click on a link in the Top Performance Improvement Targets
• Watch the browser window opens a new tab

Expected Behaviour

• Navigate to the Nerdlet
• Click on a link in the Top Performance Improvement Targets
• Only open the detailed stacked nerdlet

Relevant Logs / Console output

Your Environment

• NR1 CLI version used:
• Browser name and version:
• Operating System and version:

Additional context

Refactor the use of PlatformStateContext, NerdletStateContext, and AutoSizer in the root Nerdlet

The usage of those components falls outside of best practice and needs a slight refactor.

Unable to use custom dates with this nerdpack

Description

The nerdpack throws errors when I use time picker for a custom date. Let's say I pick start time as Nov 5th 1.05 pm - Nov 5th 2.05 pm. The nerdpack throws an error which seems wrong because it complains start time must be before end time (which in this case it obviously is).

Steps to Reproduce

Load Site/Browser Analyser and click time picker to select custom time
Pick start time as Nov 5th 1.05 pm or whichever date that suits
Pick end time as Nov 5th 2.05 pm or any date that suits
Note in this case, there is a 1 hour window selected.
Now, submit your time input and you would see an error render on the page

Expected Behaviour

I should see the customer sentiments breakdown for that time divided into 3 buckets (Satisfied, Tolerating and Frustrated, plus optimisation recommendations).

Relevant Logs / Console output

Your Environment

• NR1 CLI version used: @datanerd/nr1/1.2.2 darwin-x64 node-v10.16.3
• Browser name and version: various (mostly Chrome, Firefox, Safari and IE)
• Operating System and version: Mac OS 10.14.6

Additional context

add HelpModal component

NR1 library deprecation issues

Repolinter Report

This report was generated automatically by the Repolinter.

This Repolinter run generated the following results:

❗ Error	❌ Fail	⚠️ Warn	✅ Pass	Ignored	Total
0	0	1	6	0	7

• Warning
  • ⚠️ nr1-lib-deprecation-tablerow-actions-icontype
• Passed
  • ✅ nr1-lib-deprecation-dropdown-label
  • ✅ nr1-lib-deprecation-accountpicker-onchange
  • ✅ nr1-lib-deprecation-icon-sizetype
  • ✅ nr1-lib-deprecation-entity-title-table-row-cell-value-reporting
  • ✅ nr1-lib-deprecation-tooltip-classname
  • ✅ nr1-lib-deprecation-tooltip-style

Warning #

Click to see rules

⚠️ nr1-lib-deprecation-tablerow-actions-icontype #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/table-row. For more information please visit newrelic/developer-website#1033. Below is a list of files or patterns that failed:

• nerdlets/shared/components/breakdown.js: Contains The iconType property of the actions object should not be present within a TableRow.

Passed #

Click to see rules

✅ nr1-lib-deprecation-dropdown-label #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/dropdown. For more information please visit newrelic/developer-website#1033. All files passed this test.

✅ nr1-lib-deprecation-accountpicker-onchange #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/account-picker. For more information please visit newrelic/developer-website#1033. All files passed this test.

✅ nr1-lib-deprecation-icon-sizetype #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/icon. For more information please visit newrelic/developer-website#1033. All files passed this test.

✅ nr1-lib-deprecation-entity-title-table-row-cell-value-reporting #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/entity-title-table-row-cell. For more information please visit newrelic/developer-website#1033. All files passed this test.

✅ nr1-lib-deprecation-tooltip-classname #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/tooltip. For more information please visit newrelic/developer-website#1033. All files passed this test.

✅ nr1-lib-deprecation-tooltip-style #

See the New Relic Developer docs for current API details https://developer.newrelic.com/components/tooltip. For more information please visit newrelic/developer-website#1033. All files passed this test.

Replace moment lib in the project

Moment is inappropriately costly for the benefit to this project.

We need to refactor:

• https://github.com/newrelic/nr1-browser-analyzer/blob/802e38573a0f890be05ab6a276e7f23fd371856d/component/stat-utils.js
• https://github.com/newrelic/nr1-browser-analyzer/blob/8d278879d6008839cf01da4e6847f3d846e0f35f/nerdlets/shared/components/stat-utils.js

When you click into a link from the table, the heading of the stacked nerdlet should be a link

It would be helpful to actually go visit the url without needing to copy and paste it.

Refactor Nerdlet use of Platform and Nerdlet StateContext

[Repolinter] Open Source Policy Issues

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

❗ Error	❌ Fail	⚠️ Warn	✅ Pass	Ignored	Total
0	0	0	13	0	13

• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-starts-with-nr1-catalog-header
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ readme-contains-discuss-topic
  • ✅ third-party-notices-file-exists
  • ✅ code-of-conduct-should-not-exist-here
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists
  • ✅ package-scripts-present

Passed #

Click to see rules

✅ license-file-exists #

Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.

✅ readme-file-exists #

Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.

✅ readme-starts-with-nr1-catalog-header #

The first 1 lines contain all of the requested patterns. (README.md). The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/.

✅ readme-contains-security-section #

Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-link-to-security-policy #

Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-discuss-topic #

Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ third-party-notices-file-exists #

Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ code-of-conduct-should-not-exist-here #

New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Did not find a file matching the specified patterns. All files passed this test.

✅ github-actions-workflow-file-exists #

Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ nr1-catalog-config-file-exists #

Found file (catalog/config.json).

✅ nr1-catalog-screenshots-directory-exists #

Found file (catalog/screenshots).

✅ nr1-catalog-documentation-file-exists #

Found file (catalog/documentation.md).

✅ package-scripts-present #

An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.

UpStream Service is not showing the corresponding workload of the application

Hi Team,

When I am clicking on the Upstream service from the site analyzer page, it is getting redirected to the whole environment workload instead of the corresponding application workload.

Upgrade the project meta data to support new catalog commands

Add metadata to the repository that matches the example laid out here.

• Add a config.json file to a catalog directory in the repo root, matching this format.
• Move the /screenshots directory into catalog:
  • Update the screenshot file names (to match this format)
  • Update the screenshot links in the README.md.
• (Optional) If there's additional documentation referenced in the repo, add a additionalInfo.md file to a catalog directory in the repo root, matching this format.
• Add one or more screenshots to a catalog/screenshots directory in the repo root, matching this format.
• Update the relative paths in documentation.md to be absolute paths
• Add the new header image to the top of README.md and catalog/documentation.md.
• Ensure the README.md commands section matches this.
• Run npm start and let the CLI move the nr1.json
  • Edit that file to make sure the name and description make sense.

App not visible in New Relic ONE when locally served or published

I followed the steps provided for installation and am able to get the app built, published, deployed and subscribed to.

Here are my results with all apps I've tried to publish so far:
SUCCESSES:
nr1-cloud-optimize
nr1-container-explorer
nr1-customer-journey
nr1-datalyzer
nr1-groundskeeper
nr1-neon

FAILURES:
nr1-event-stream
nr1-browser-analyzer Issue: #13
nr1-top Issue: newrelic/nr1-top#9

---

OUTPUT: nr1 nerdpack:info --verbose

init version: @oclif/[email protected] argv: [ '--verbose', [length]: 1 ]
Fetching info from registry...
Request: POST https://artifact-registry.service.newrelic.com/graphql
Data: 'query {\n package(uuid: ' +
'"a19f7cc1-918b-4c65-9d71-bc67320a044c") {\n ' +
' uuid\n accountId\n ' +
' publications {\n createdAt\n ' +
' createdByUser\n ' +
'version\n }\n }\n ' +
' packageDeployments(uuid: ' +
'"a19f7cc1-918b-4c65-9d71-bc67320a044c") {\n ' +
' channel\n deployedPublication {\n ' +
' version\n }\n ' +
' }\n }'
Headers: {
'API-Key': '',
'Content-Type': 'application/graphql'
}

Registry: Present
Id: a19f7cc1-918b-4c65-9d71-bc67320a044c
Region: us
Account ID: 1847652
Local version: 0.1.6

Version Date Deployed to channel
0.1.6 3 minutes ago DEV

---

LOCAL SERVER EXECUTION
STEP: Install
npm install

STEP: Run locally
npm start

STEP: Test
https://one.newrelic.com/?nerdpacks=local

RESULT: App Not Displayed

PUBLISH TO NEW RELIC ONE

STEP: Create a new UUID
nr1 nerdpack:uuid -gf
GGenerated id is a19f7cc1-918b-4c65-9d71-bc67320a044c

STEP: Force publish, override version if exists
nr1 nerdpack:publish -f

STEP: Deploy to DEV
nr1 nerdpack:deploy --channel=DEV

STEP: Subscribe to DEV
nr1 nerdpack:subscribe --channel=DEV

STEP: Check info
nr1 nerdpack:info --verbose

Version Date Deployed to channel
0.1.5 4 minutes ago DEV

RESULT: App Not Displayed

What additional information should I provide to help with troubleshooting?

add Messages component

Tracking: Add support for SPA's

The current version of the app looks only at PageView data and does have support for SPA's. Creating a capability to toggle b/w SPA and general web application and saving that preference with the entity is purpose of this issue.

• Query the PageView and BrowserInteraction events to determine a default mode
• Add a toggle feature to the page to transition b/w measurement methodologies
• Saving (and loading) that context via entity-scoped NerdStorage

This issue is a collaboration with @ShuJackson who prototyped this solution here: https://github.com/ShuJackson/nr1-browser-analyzer

Scrollbars in the spark charts

scrollbars appear at the bottom left side of each of the spark charts on the top.

[Repolinter] Open Source Policy Issues

Repolinter Report

🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.

This Repolinter run generated the following results:

❗ Error	❌ Fail	⚠️ Warn	✅ Pass	Ignored	Total
0	0	0	13	0	13

• Passed
  • ✅ license-file-exists
  • ✅ readme-file-exists
  • ✅ readme-starts-with-nr1-catalog-header
  • ✅ readme-contains-security-section
  • ✅ readme-contains-link-to-security-policy
  • ✅ readme-contains-discuss-topic
  • ✅ third-party-notices-file-exists
  • ✅ code-of-conduct-file-does-not-exist
  • ✅ github-actions-workflow-file-exists
  • ✅ nr1-catalog-config-file-exists
  • ✅ nr1-catalog-screenshots-directory-exists
  • ✅ nr1-catalog-documentation-file-exists
  • ✅ package-scripts-present

Passed #

Click to see rules

✅ license-file-exists #

Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.

✅ readme-file-exists #

Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.

✅ readme-starts-with-nr1-catalog-header #

The first 1 lines contain all of the requested patterns. (README.md). The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/.

✅ readme-contains-security-section #

Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-link-to-security-policy #

Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ readme-contains-discuss-topic #

Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.

✅ third-party-notices-file-exists #

Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ code-of-conduct-file-does-not-exist #

New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Did not find a file matching the specified patterns. All files passed this test.

✅ github-actions-workflow-file-exists #

Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.

✅ nr1-catalog-config-file-exists #

Found file (catalog/config.json).

✅ nr1-catalog-screenshots-directory-exists #

Found file (catalog/screenshots).

✅ nr1-catalog-documentation-file-exists #

Found file (catalog/documentation.md).

✅ package-scripts-present #

An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.