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.

Sign up for GitHub

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

Jump to bottom

Generate NewRelic beacons from the frontend #2696

Closed
2 tasks
mdragon opened this issue Nov 1, 2024 · 3 comments · Fixed by #2922
Closed
2 tasks

Generate NewRelic beacons from the frontend #2696

mdragon opened this issue Nov 1, 2024 · 3 comments · Fixed by #2922
Assignees
@doug-s-nava

Comments

@mdragon
Copy link
Collaborator

mdragon commented Nov 1, 2024 •
edited by mxk0
Loading

Summary

Implement in our client code
https://docs.newrelic.com/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing/

Acceptance criteria

  • Frontend has the NewRelic library
  • Frontend is sending browser data requests using NewRelic library
@mdragon mdragon moved this from Icebox to Todo in Simpler.Grants.gov Product Backlog Nov 1, 2024
@coilysiren
Copy link
Collaborator

😍

@coilysiren coilysiren self-assigned this Nov 7, 2024
@mxk0
Copy link
Collaborator

mxk0 commented Nov 12, 2024

@coilysiren just a heads up from when you froze during sprint planning, one of the frontend folks is going to pick this up.

@mxk0 mxk0 changed the title Implement New Relic Browser Data Distributed Tracing Generate NewRelic beacons from the frontend Nov 12, 2024
@mxk0 mxk0 mentioned this issue Nov 13, 2024
Closed
@doug-s-nava doug-s-nava self-assigned this Nov 18, 2024
This was referenced Nov 19, 2024
Merged
Open
@doug-s-nava
Copy link
Collaborator

Some questions answered:

  • is there a way to fully test this without deploying to DEV? can we deploy this to DEV to test?
    • we will deploy to DEV prior to merge to test effectiveness
  • naming scheme for app names
    • we will use an <appname>-<env> standard to allow for easy machine usage, and add human readable aliases as necessary
  • licenses
    • we will have 4 admin users, 5 non-admin users
  • license key usage (per app / per env / shared?)
    • one is fine
  • deployment strategy / are we ok with going to staging and prod with this, or are there volume concerns?
    • it's ok to go PROD - if we exceed our quota it'll just stop collecting
  • how important is it to support new relic locally / in local containers
    • not very
  • next steps if any on New Relic typing
  • where / how to document
    • I'll start with a readme

@mdragon mdragon mentioned this issue Nov 22, 2024
Merged
mdragon added a commit that referenced this issue Nov 22, 2024
@mdragon
[Issue #2696] Allow frontend-infra to be kicked off manually (#2993)
71e217d 
## Summary
Supports #2696

### Time to review: __1 mins__

## Changes proposed
Allow Frontend Infra to be deployed via the Action Workflow
doug-s-nava added a commit that referenced this issue Nov 26, 2024
@doug-s-nava
[Issue #2696] add New Relic to Next app (#2922)
f51f5db 
* code added as per direction from New Relic documentation and example Next app in order to add necessary fronted scripts for tracking timing
* custom typing added to plaster over deficiencies in supplied New Relic TS definitions
* support for necessary environment variables added in infra code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@doug-s-nava doug-s-nava

Labels
None yet
Projects
Simpler.Grants.gov Product Backlog
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Issue #2696] add New Relic to Next app HHS/simpler-grants-gov
4 participants
@mdragon @mxk0 @coilysiren @doug-s-nava